Communication device

ABSTRACT

The communication device comprising a power-off notification implementer, a power-off location notifying implementer, a header displaying implementer, a footer displaying implementer, a zone leaving notifying implementer, and a zone entering notifying implementer.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Ser. No. 12/978,569 filed2010 Dec. 26, which is a continuation of U.S. Ser. No. 11/743,776 filed2007 May 3, all of which are hereby incorporated herein by reference intheir entirety.

BACKGROUND OF INVENTION

The invention relates to communication device and more particularly tothe communication device which is capable to communicate with anothercommunication device in a wireless fashion.

U.S. Patent Publication No. 20030045301 is introduced as a prior art ofthe present invention of which the summary is the following: “Thepresent invention is directed to an electronic system and method formanaging location, calendar, and event information. The system comprisesat least two hand portable electronic devices, each having a displaydevice to display personal profile, location, and event information, andmeans for processing, storing, and wirelessly communicating data. Asoftware program running in the electronic device can receive local andremote input data; store, process, and update personal profile, event,time, and location information; and convert location information intocoordinates of a graphic map display. The system additionally includesat least one earth orbiting satellite device using remote sensingtechnology to determine the location coordinates of the electronicdevice. The electronic devices receive synchronization messagesbroadcast by the satellite device, causing the software program toupdate the personal profile, event, time, and location informationstored in each hand portable electronic device”. However, this prior artdoes not disclose the communication device comprising a power-offnotification implementer, a power-off location notifying implementer, aheader displaying implementer, a footer displaying implementer, a zoneleaving notifying implementer, and a zone entering notifyingimplementer.

For the avoidance of doubt, the number of the prior arts introducedherein (and/or in IDS) may be of a large one, however, applicant has nointent to hide the more relevant prior art(s) in the less relevant ones.

SUMMARY OF INVENTION

It is an object of the present invention to provide a device capable toimplement a plurality of functions.

It is another object of the present invention to provide merchandise tomerchants attractive to the customers in the U.S.

It is another object of the present invention to provide mobility to theusers of communication device.

It is another object of the present invention to provide moreconvenience to the customers in the U.S.

It is another object of the present invention to provide moreconvenience to the users of communication device or any tangible thingin which the communication device is fixedly or detachably (i.e.,removably) installed.

It is another object of the present invention to overcome theshortcomings associated with the foregoing prior arts.

It is another object of the present invention to provide a devicecapable to implement a plurality of functions.

The present invention introduces the communication device comprising apower-off notification implementer, a power-off location notifyingimplementer, a header displaying implementer, a footer displayingimplementer, a zone leaving notifying implementer, and a zone enteringnotifying implementer.

BRIEF DESCRIPTION OF DRAWINGS

The above and other aspects, features, and advantages of the inventionwill be better understood by reading the following more particulardescription of the invention, presented in conjunction with thefollowing drawing, wherein:

FIG. 1 is a block diagram illustrating an exemplary embodiment of thepresent invention.

DETAILED DESCRIPTION

The following description is of the best presently contemplated mode ofcarrying out the present invention. This description is not to be takenin a limiting sense but is made merely for the purpose of describing thegeneral principles of the invention. For example, each description ofrandom access memory in this specification illustrate(s) only onefunction or mode in order to avoid complexity in its explanation,however, such description does not mean that only one function or modecan be implemented at a time. In other words, more than one function ormode can be implemented simultaneously by way of utilizing the samerandom access memory. In addition, the figure number is cited after theelements in parenthesis in a manner for example ‘RAM 206 (FIG. 1)’. Itis done so merely to assist the readers to have a better understandingof this specification, and must not be used to limit the scope of theclaims in any manner since the figure numbers cited are not exclusive.There are only few data stored in each storage area described in thisspecification. This is done so merely to simplify the explanation and,thereby, to enable the reader of this specification to understand thecontent of each function with less confusion. Therefore, more than fewdata (hundreds and thousands of data, if necessary) of the same kind,not to mention, are preferred to be stored in each storage area to fullyimplement each function described herein. The scope of the inventionshould be determined by referencing the appended claims.

FIG. 1 is a simplified block diagram of the Communication Device 200utilized in the present invention. Referring to FIG. 1, CommunicationDevice 200 includes CPU 211 which controls and administers the overallfunction and operation of Communication Device 200. CPU 211 uses RAM 206to temporarily store data and/or to perform calculation to perform itsfunction, and to implement the present invention, modes, functions, andsystems explained hereinafter. Video Processor 202 generates analogand/or digital video signals which are displayed on LCD 201. ROM 207stores the data and programs which are essential to operateCommunication Device 200. Wireless signals are received by Antenna 218and processed by Signal Processor 208. Input signals are input by InputDevice 210, such as a dial pad, a joystick, and/or a keypad, and thesignals are transferred via Input Interface 209 and Data Bus 203 to CPU211. Indicator 212 is an LED lamp which is designed to output differentcolors (e.g., red, blue, green, etc). Analog audio data is input toMicrophone 215. A/D 213 converts the analog audio data into a digitalformat. Speaker 216 outputs analog audio data which is converted into ananalog format from digital format by D/A 204. Sound Processor 205produces digital audio signals that are transferred to D/A 204 and alsoprocesses the digital audio signals transferred from A/D 213. CCD Unit214 captures video image which is stored in RAM 206 in a digital format.Vibrator 217 vibrates the entire device by the command from CPU 211.

As another embodiment, LCD 201 or LCD 201/Video Processor 202 may beseparated from the other elements described in FIG. 1, and be connectedin a wireless fashion to be wearable and/or head-mountable.

When Communication Device 200 is in the voice communication mode, theanalog audio data input to Microphone 215 is converted to a digitalformat by A/D 213 and transmitted to another device via Antenna 218 in awireless fashion after being processed by Signal Processor 208, and thewireless signal representing audio data which is received via Antenna218 is output from Speaker 216 after being processed by Signal Processor208 and converted to analog signal by D/A 204. For the avoidance ofdoubt, the definition of Communication Device 200 in this specificationincludes so-called ‘PDA’. The definition of Communication Device 200also includes in this specification any device which is mobile and/orportable and which is capable to send and/or receive audio data, textdata, image data, video data, and/or other types of data in a wirelessfashion via Antenna 218. The definition of Communication Device 200further includes any micro device embedded or installed into devices andequipments (e.g., VCR, TV, tape recorder, heater, air conditioner, fan,clock, micro wave oven, dish washer, refrigerator, oven, washingmachine, dryer, door, window, automobile, motorcycle, and modem) toremotely control these devices and equipments. The size of CommunicationDevice 200 is irrelevant. Communication Device 200 may be installed inhouses, buildings, bridges, boats, ships, submarines, airplanes, andspaceships, and firmly fixed therein.

This paragraph illustrate(s) the elements of Communication Device 200.The elements of Communication Device 200 described in this paragraph isidentical to the ones described in FIG. 1, except Communication Device200 has new element, i.e., LED 219. Here, LED 219 receives infra redsignals from other wireless devices, which are transferred to CPU 211via Data Bus 203. LED 219 also sends infra red signals in a wirelessfashion which are composed by CPU 211 and transferred via Data Bus 203.As the second embodiment, LED 219 may be connected to Signal Processor208. Here, LED 219 transfers the received infra red signals to SignalProcessor 208, and Signal Processor 208 processes and converts thesignals to a CPU readable format which are transferred to CPU 211 viaData Bus 203. The data produced by CPU 211 are processed by SignalProcessor 208 and transferred to another device via LED 219 in awireless fashion. The task of LED 219 is as same as that of Antenna 218described in FIG. 1 except that LED 219 utilizes infra red signals forimplementing wireless communication in the second embodiment. For theavoidance of doubt, the reference to FIG. 1 (e.g., referring to FIG. 1in parenthesis) automatically refers to this paragraph in thisspecification.

This paragraph illustrate(s) the data stored in Host H. In the presentembodiment, Host H includes Host Information Storage Area H00 a whichstores various types of data to assist and/or co-operate withCommunication Device 200 to implement all modes, functions, and systemsdescribed in this specification. As another embodiment, Host H may becomposed of a plurality of computers, i.e., one master computer and aplurality of slave computers, wherein the master computer is connectedto the plurality of slave computers. As another embodiment, Host H mayalso be composed of a plurality of master computers by way of utilizingpeer-to-peer connection.

<<Header Displaying Function>>

The following paragraphs illustrate the header displaying function,wherein when a document is displayed on LCD 201 (FIG. 1), the header isdisplayed in the document. The text of the header is identified byCommunication Device 200. The font type of the header is identified byCommunication Device 200. The font size of the header is identified byCommunication Device 200. The font color of the header is identified byCommunication Device 200. The location of the header displayed in thedocument is identified by Communication Device 200. The document and thetext, font type, font size, font color, and location of the header aretransferred to another device, and the another device displays thedocument with the header in accordance with the text, font type, fontsize, font color, and location received. Here, the header (or thedocument header) is the common text displayed at the upper portion ofeach page of a document. The header may indicate the title of thedocument.

This paragraph illustrates the major elements utilized to implement thepresent function. In this embodiment, Host H is connected to Network NT(e.g., the Internet). Device A, a Communication Device 200, is connectedto Network NT (e.g., the Internet) in a wireless fashion. Device B,another Communication Device 200, is connected to Network NT (e.g., theInternet) in a wireless fashion. Host H, Device A, and Device B arecapable to communicate with each other via Network NT (e.g., theInternet) to implement the present function. Device A and Device B arealso capable to communicate with each other directly in a wirelessfashion to implement the present function.

This paragraph illustrates the storage area included in Host H. In thisembodiment, Host H includes Header Displaying Information Storage AreaH549 a of which the data and the software program(s) stored therein aredescribed hereinafter.

This paragraph illustrates the storage area(s) included in HeaderDisplaying Information Storage Area H549 a. In this embodiment, HeaderDisplaying Information Storage Area H549 a includes Header DisplayingData Storage Area H549 b and Header Displaying Software Storage AreaH549 c. Header Displaying Data Storage Area H549 b stores the datanecessary to implement the present function on the side of Host H, suchas the one(s) described hereinafter. Header Displaying Software StorageArea H549 c stores the software program(s) necessary to implement thepresent function on the side of Host H, such as the one(s) describedhereinafter.

This paragraph illustrates the storage area(s) included in HeaderDisplaying Data Storage Area H549 b. In this embodiment, HeaderDisplaying Data Storage Area H549 b includes Document Data Storage AreaH549 b 1, Header Preselected Data Storage Area H549 b 2, User SelectedData Storage Area H549 b 3, and Work Area H549 b 4. Document DataStorage Area H549 b 1 stores the document data which is the documentcapable to be displayed on LCD 201 (FIG. 1). The document may be the onewhich is produced by a word processing software (e.g., MS Word). HeaderPreselected Data Storage Area H549 b 2 stores the data describedhereinafter. User Selected Data Storage Area H549 b 3 stores the datadescribed hereinafter. Work Area H549 b 4 is utilized as a work area toperform calculation and temporarily store data.

This paragraph illustrates the storage area(s) included in HeaderPreselected Data Storage Area H549 b 2. In this embodiment, HeaderPreselected Data Storage Area H549 b 2 includes Header Preselected TextData Storage Area H549 b 2 a, Header Preselected Font Type Data StorageArea H549 b 2 b, Header Preselected Font Size Data Storage Area H549 b 2c, Header Preselected Font Color Data Storage Area H549 b 2 d, andHeader Preselected Location Data Storage Area H549 b 2 e. HeaderPreselected Text Data Storage Area H549 b 2 a stores the data describedhereinafter. Header Preselected Font Type Data Storage Area H549 b 2 bstores the data described hereinafter. Header Preselected Font Size DataStorage Area H549 b 2 c stores the data described hereinafter. HeaderPreselected Font Color Data Storage Area H549 b 2 d stores the datadescribed hereinafter. Header Preselected Location Data Storage AreaH549 b 2 e stores the data described hereinafter.

This paragraph illustrates the data stored in Header Preselected TextData Storage Area H549 b 2 a. In this embodiment, Header PreselectedText Data Storage Area H549 b 2 a comprises two columns, i.e., ‘HeaderPreselected Text ID’ and ‘Header Preselected Text Data’. Column ‘HeaderPreselected Text ID’ stores the header preselected text IDs, and eachheader preselected text ID is an identification of the correspondingheader preselected text data stored in column ‘Header Preselected TextData’. Each header preselected text ID may indicate the name or title ofthe corresponding header preselected text data. Column ‘HeaderPreselected Text Data’ stores the header preselected text data, and eachheader preselected text data is the text data capable to be utilized asheader of a document. In this embodiment, Header Preselected Text DataStorage Area H549 b 2 a stores the following data: ‘Header PreselectedText#1’ and the corresponding ‘Header Preselected Text Data#1’; ‘HeaderPreselected Text#2’ and the corresponding ‘Header Preselected TextData#2’; ‘Header Preselected Text#3’ and the corresponding ‘HeaderPreselected Text Data#3’; and ‘Header Preselected Text#4’ and thecorresponding ‘Header Preselected Text Data#4’.

This paragraph illustrates the data stored in Header Preselected FontType Data Storage Area H549 b 2 b. In this embodiment, HeaderPreselected Font Type Data Storage Area H549 b 2 b comprises twocolumns, i.e., ‘Header Preselected Font Type ID’ and ‘Header PreselectedFont Type Data’. Column ‘Header Preselected Font Type ID’ stores theheader preselected font type IDs, and each header preselected font typeID is an identification of the corresponding header preselected fonttype data stored in column ‘Header Preselected Font Type Data’. Eachheader preselected font type ID may indicate the name or title of thecorresponding header preselected font type data. Column ‘HeaderPreselected Font Type Data’ stores the header preselected font typedata, and each header preselected font type data indicates a specificfont type, such as Arial, Times New Roman, Tahoma, or Gothic. In thisembodiment, Header Preselected Font Type Data Storage Area H549 b 2 bstores the following data: ‘Header Preselected Font Type#1’ and thecorresponding ‘Header Preselected Font Type Data#1’; ‘Header PreselectedFont Type#2’ and the corresponding ‘Header Preselected Font TypeData#2’; ‘Header Preselected Font Type#3’ and the corresponding ‘HeaderPreselected Font Type Data#3’; and ‘Header Preselected Font Type#4’ andthe corresponding ‘Header Preselected Font Type Data#4’.

This paragraph illustrates the data stored in Header Preselected FontSize Data Storage Area H549 b 2 c. In this embodiment, HeaderPreselected Font Size Data Storage Area H549 b 2 c comprises twocolumns, i.e., ‘Header Preselected Font Size ID’ and ‘Header PreselectedFont Size Data’. Column ‘Header Preselected Font Size ID’ stores theheader preselected font size IDs, and each header preselected font sizeID is an identification of the corresponding header preselected fontsize data stored in column ‘Header Preselected Font Size Data’. Eachheader preselected font size ID may indicate the name or title of thecorresponding header preselected font size data. Column ‘HeaderPreselected Font Size Data’ stores the header preselected font sizedata, and each header preselected font size data indicates a specificfont size, such as 8 points, 10 points, 14 points, or 18 points. In thisembodiment, Header Preselected Font Size Data Storage Area H549 b 2 cstores the following data: ‘Header Preselected Font Size#1’ and thecorresponding ‘Header Preselected Font Size Data#1’; ‘Header PreselectedFont Size#2’ and the corresponding ‘Header Preselected Font SizeData#2’; ‘Header Preselected Font Size#3’ and the corresponding ‘HeaderPreselected Font Size Data#3’; and ‘Header Preselected Font Size#4’ andthe corresponding ‘Header Preselected Font Size Data#4’.

This paragraph illustrates the data stored in Header Preselected FontColor Data Storage Area H549 b 2 d. In this embodiment, HeaderPreselected Font Color Data Storage Area H549 b 2 d comprises twocolumns, i.e., ‘Header Preselected Font Color ID’ and ‘HeaderPreselected Font Color Data’. Column ‘Header Preselected Font Color ID’stores the header preselected font color IDs, and each headerpreselected font color ID is an identification of the correspondingheader preselected font color data stored in column ‘Header PreselectedFont Color Data’. Each header preselected font color ID may indicate thename or title of the corresponding header preselected font color data.Column ‘Header Preselected Font Color Data’ stores the headerpreselected font color data, and each header preselected font color dataindicates a specific font color, such as red, blue, green or yellow. Inthis embodiment, Header Preselected Font Color Data Storage Area H549 b2 d stores the following data: ‘Header Preselected Font Color#1’ and thecorresponding ‘Header Preselected Font Color Data#1’; ‘HeaderPreselected Font Color#2’ and the corresponding ‘Header Preselected FontColor Data#2; Header Preselected Font Color#3’ and the corresponding‘Header Preselected Font Color Data#3’; and ‘Header Preselected FontColor#4’ and the corresponding ‘Header Preselected Font Color Data#4’.

This paragraph illustrates the data stored in Header PreselectedLocation Data Storage Area H549 b 2 e. In this embodiment, HeaderPreselected Location Data Storage Area H549 b 2 e comprises two columns,i.e., ‘Header Preselected Location ID’ and ‘Header Preselected LocationData’. Column ‘Header Preselected Location ID’ stores the headerpreselected location IDs, and each header preselected location ID is anidentification of the corresponding header preselected location datastored in column ‘Header Preselected Location Data’. Each headerpreselected location ID indicates the name or title of the correspondingheader preselected location data. Column ‘Header Preselected LocationData’ stores the header preselected location data, and each headerpreselected location data indicates the location at which the header isdisplayed in the document data. In this embodiment, Header PreselectedLocation Data Storage Area H549 b 2 e stores the following data: ‘HeaderPreselected Location#1’ and the corresponding ‘Header PreselectedLocation Data#1’; ‘Header Preselected Location#2’ and the corresponding‘Header Preselected Location Data#2; Header Preselected Location#3’ andthe corresponding ‘Header Preselected Location Data#3’; and ‘HeaderPreselected Location#4’ and the corresponding ‘Header PreselectedLocation Data#4’.

This paragraph illustrates the storage area(s) included in User SelectedData Storage Area H549 b 3. In this embodiment, User Selected DataStorage Area H549 b 3 includes Header Text Data Storage Area H549 b 3 a,Header Font Type Data Storage Area H549 b 3 b, Header Font Size DataStorage Area H549 b 3 c, Header Font Color Data Storage Area H549 b 3 d,and Header Location Data Storage Area H549 b 3 e. Header Text DataStorage Area H549 b 3 a stores the header text data which is one of theheader preselected text data selected by the user. Header Font Type DataStorage Area H549 b 3 b stores the header font type data which is one ofthe header preselected font type data selected by the user. Header FontSize Data Storage Area H549 b 3 c stores the header font size data whichis one of the header preselected font size data selected by the user.Header Font Color Data Storage Area H549 b 3 d stores the header fontcolor data which is one of the header preselected font color dataselected by the user. Header Location Data Storage Area H549 b 3 estores the header location data which is one of the header preselectedlocation data selected by the user.

This paragraph illustrates the software program(s) stored in HeaderDisplaying Software Storage Area H549 c. In this embodiment, HeaderDisplaying Software Storage Area H549 c stores Header Text DataProducing Software H549 c 1, Header Font Type Data Producing SoftwareH549 c 2, Header Font Size Data Producing Software H549 c 3, Header FontColor Data Producing Software H549 c 4, Header Location Data ProducingSoftware H549 c 5, Document Header Displaying Software H549 c 6,Document Data Transferring Software H549 c 7, Header Text DataTransferring Software H549 c 8, Header Font Type Data TransferringSoftware H549 c 9, Header Font Size Data Transferring Software H549 c10, Header Font Color Data Transferring Software H549 c 11, HeaderLocation Data Transferring Software H549 c 12, and Document Package DataTransferring Software H549 c 13. Header Text Data Producing SoftwareH549 c 1 is the software program described hereinafter. Header Font TypeData Producing Software H549 c 2 is the software program describedhereinafter. Header Font Size Data Producing Software H549 c 3 is thesoftware program described hereinafter. Header Font Color Data ProducingSoftware H549 c 4 is the software program described hereinafter. HeaderLocation Data Producing Software H549 c 5 is the software programdescribed hereinafter. Document Header Displaying Software H549 c 6 isthe software program described hereinafter. Document Data TransferringSoftware H549 c 7 is the software program described hereinafter. HeaderText Data Transferring Software H549 c 8 is the software programdescribed hereinafter. Header Font Type Data Transferring Software H549c 9 is the software program described hereinafter. Header Font Size DataTransferring Software H549 c 10 is the software program describedhereinafter. Header Font Color Data Transferring Software H549 c 11 isthe software program described hereinafter. Header Location DataTransferring Software H549 c 12 is the software program describedhereinafter. Document Package Data Transferring Software H549 c 13 isthe software program described hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device A. In this embodiment, RAM 206 includes Header DisplayingInformation Storage Area 206A549 a of which the data and the softwareprogram(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device A.

This paragraph illustrates the storage area(s) included in HeaderDisplaying Information Storage Area 206A549 a. In this embodiment,Header Displaying Information Storage Area 206A549 a includes HeaderDisplaying Data Storage Area 206A549 b and Header Displaying SoftwareStorage Area 206A549 c. Header Displaying Data Storage Area 206A549 bstores the data necessary to implement the present function on the sideof Device A, such as the one(s) described hereinafter. Header DisplayingSoftware Storage Area 206A549 c stores the software program(s) necessaryto implement the present function on the side of Device A, such as theone(s) described hereinafter.

This paragraph illustrates the storage area(s) included in HeaderDisplaying Data Storage Area 206A549 b. In this embodiment, HeaderDisplaying Data Storage Area 206A549 b includes Document Data StorageArea 206A549 b 1, Header Preselected Data Storage Area 206A549 b 2, UserSelected Data Storage Area 206A549 b 3, and Work Area 206A549 b 4.Document Data Storage Area 206A549 b 1 stores the document data which isthe document capable to be displayed on LCD 201 (FIG. 1). The documentmay be the one which is produced by a word processing software (e.g., MSWord). Header Preselected Data Storage Area 206A549 b 2 stores the datadescribed hereinafter. User Selected Data Storage Area 206A549 b 3stores the data described hereinafter. Work Area 206A549 b 4 is utilizedas a work area to perform calculation and temporarily store data.

This paragraph illustrates the storage area(s) included in HeaderPreselected Data Storage Area 206A549 b 2. In this embodiment, HeaderPreselected Data Storage Area 206A549 b 2 includes Header PreselectedText Data Storage Area 206A549 b 2 a, Header Preselected Font Type DataStorage Area 206A549 b 2 b, Header Preselected Font Size Data StorageArea 206A549 b 2 c, Header Preselected Font Color Data Storage Area206A549 b 2 d, and Header Preselected Location Data Storage Area 206A549b 2 e. Header Preselected Text Data Storage Area 206A549 b 2 a storesthe data described hereinafter. Header Preselected Font Type DataStorage Area 206A549 b 2 b stores the data described hereinafter. HeaderPreselected Font Size Data Storage Area 206A549 b 2 c stores the datadescribed hereinafter. Header Preselected Font Color Data Storage Area206A549 b 2 d stores the data described hereinafter. Header PreselectedLocation Data Storage Area 206A549 b 2 e stores the data describedhereinafter.

This paragraph illustrates the data stored in Header Preselected TextData Storage Area 206A549 b 2 a. In this embodiment, Header PreselectedText Data Storage Area 206A549 b 2 a comprises two columns, i.e.,‘Header Preselected Text ID’ and ‘Header Preselected Text Data’. Column‘Header Preselected Text ID’ stores the header preselected text IDs, andeach header preselected text ID is an identification of thecorresponding header preselected text data stored in column ‘HeaderPreselected Text Data’. Each header preselected text ID may indicate thename or title of the corresponding header preselected text data. Column‘Header Preselected Text Data’ stores the header preselected text data,and each header preselected text data is the text data capable to beutilized as header of a document. In this embodiment, Header PreselectedText Data Storage Area 206A549 b 2 a stores the following data: ‘HeaderPreselected Text#1’ and the corresponding ‘Header Preselected TextData#1’; ‘Header Preselected Text#2’ and the corresponding HeaderPreselected Text Data#2; ‘Header Preselected Text#3’ and thecorresponding ‘Header Preselected Text Data#3’; and ‘Header PreselectedText#4’ and the corresponding ‘Header Preselected Text Data#4’.

This paragraph illustrates the data stored in Header Preselected FontType Data Storage Area 206A549 b 2 b. In this embodiment, HeaderPreselected Font Type Data Storage Area 206A549 b 2 b comprises twocolumns, i.e., ‘Header Preselected Font Type ID’ and ‘Header PreselectedFont Type Data’. Column ‘Header Preselected Font Type ID’ stores theheader preselected font type IDs, and each header preselected font typeID is an identification of the corresponding header preselected fonttype data stored in column ‘Header Preselected Font Type Data’. Eachheader preselected font type ID may indicate the name or title of thecorresponding header preselected font type data. Column ‘HeaderPreselected Font Type Data’ stores the header preselected font typedata, and each header preselected font type data indicates a specificfont type, such as Arial, Times New Roman, Tahoma, or Gothic. In thisembodiment, Header Preselected Font Type Data Storage Area 206A549 b 2 bstores the following data: ‘Header Preselected Font Type#1’ and thecorresponding ‘Header Preselected Font Type Data#1’; ‘Header PreselectedFont Type#2’ and the corresponding ‘Header Preselected Font Type Data#2;Header Preselected Font Type#3’ and the corresponding ‘HeaderPreselected Font Type Data#3’; and ‘Header Preselected Font Type#4’ andthe corresponding ‘Header Preselected Font Type Data#4’.

This paragraph illustrates the data stored in Header Preselected FontSize Data Storage Area 206A549 b 2 c. In this embodiment, HeaderPreselected Font Size Data Storage Area 206A549 b 2 c comprises twocolumns, i.e., ‘Header Preselected Font Size ID’ and ‘Header PreselectedFont Size Data’. Column ‘Header Preselected Font Size ID’ stores theheader preselected font size IDs, and each header preselected font sizeID is an identification of the corresponding header preselected fontsize data stored in column ‘Header Preselected Font Size Data’. Eachheader preselected font size ID may indicate the name or title of thecorresponding header preselected font size data. Column ‘HeaderPreselected Font Size Data’ stores the header preselected font sizedata, and each header preselected font size data indicates a specificfont size, such as 8 points, 10 points, 14 points, or 18 points. In thisembodiment, Header Preselected Font Size Data Storage Area 206A549 b 2 cstores the following data: ‘Header Preselected Font Size#1’ and thecorresponding ‘Header Preselected Font Size Data#1’; ‘Header PreselectedFont Size#2’ and the corresponding ‘Header Preselected Font SizeData#2’; ‘Header Preselected Font Size#3’ and the corresponding ‘HeaderPreselected Font Size Data#3’; and ‘Header Preselected Font Size#4’ andthe corresponding ‘Header Preselected Font Size Data#4’.

This paragraph illustrates the data stored in Header Preselected FontColor Data Storage Area 206A549 b 2 d. In this embodiment, HeaderPreselected Font Color Data Storage Area 206A549 b 2 d comprises twocolumns, i.e., ‘Header Preselected Font Color ID’ and ‘HeaderPreselected Font Color Data’. Column ‘Header Preselected Font Color ID’stores the header preselected font color IDs, and each headerpreselected font color ID is an identification of the correspondingheader preselected font color data stored in column ‘Header PreselectedFont Color Data’. Each header preselected font color ID may indicate thename or title of the corresponding header preselected font color data.Column ‘Header Preselected Font Color Data’ stores the headerpreselected font color data, and each header preselected font color dataindicates a specific font color, such as red, blue, green or yellow. Inthis embodiment, Header Preselected Font Color Data Storage Area 206A549b 2 d stores the following data: ‘Header Preselected Font Color#1’ andthe corresponding ‘Header Preselected Font Color Data#1’; ‘HeaderPreselected Font Color#2’ and the corresponding ‘Header Preselected FontColor Data#2; Header Preselected Font Color#3’ and the corresponding‘Header Preselected Font Color Data#3’; and ‘Header Preselected FontColor#4’ and the corresponding ‘Header Preselected Font Color Data#4’.

This paragraph illustrates the data stored in Header PreselectedLocation Data Storage Area 206A549 b 2 e. In this embodiment, HeaderPreselected Location Data Storage Area 206A549 b 2 e comprises twocolumns, i.e., ‘Header Preselected Location ID’ and ‘Header PreselectedLocation Data’. Column ‘Header Preselected Location ID’ stores theheader preselected location IDs, and each header preselected location IDis an identification of the corresponding header preselected locationdata stored in column ‘Header Preselected Location Data’. Each headerpreselected location ID indicates the name or title of the correspondingheader preselected location data. Column ‘Header Preselected LocationData’ stores the header preselected location data, and each headerpreselected location data indicates the location at which the header isdisplayed in the document data. In this embodiment, Header PreselectedLocation Data Storage Area 206A549 b 2 e stores the following data:‘Header Preselected Location#1’ and the corresponding ‘HeaderPreselected Location Data#1’; ‘Header Preselected Location#2’ and thecorresponding ‘Header Preselected Location Data#2’; ‘Header PreselectedLocation#3’ and the corresponding ‘Header Preselected Location Data#3’;and ‘Header Preselected Location#4’ and the corresponding ‘HeaderPreselected Location Data#4’.

This paragraph illustrates the storage area(s) included in User SelectedData Storage Area 206A549 b 3. In this embodiment, User Selected DataStorage Area 206A549 b 3 includes Header Text Data Storage Area 206A549b 3 a, Header Font Type Data Storage Area 206A549 b 3 b, Header FontSize Data Storage Area 206A549 b 3 c, Header Font Color Data StorageArea 206A549 b 3 d, and Header Location Data Storage Area 206A549 b 3 e.Header Text Data Storage Area 206A549 b 3 a stores the header text datawhich is one of the header preselected text data selected by the user.Header Font Type Data Storage Area 206A549 b 3 b stores the header fonttype data which is one of the header preselected font type data selectedby the user. Header Font Size Data Storage Area 206A549 b 3 c stores theheader font size data which is one of the header preselected font sizedata selected by the user. Header Font Color Data Storage Area 206A549 b3 d stores the header font color data which is one of the headerpreselected font color data selected by the user. Header Location DataStorage Area 206A549 b 3 e stores the header location data which is oneof the header preselected location data selected by the user.

This paragraph illustrates the software program(s) stored in HeaderDisplaying Software Storage Area 206A549 c. In this embodiment, HeaderDisplaying Software Storage Area 206A549 c stores Header Text DataProducing Software 206A549 c 1, Header Font Type Data Producing Software206A549 c 2, Header Font Size Data Producing Software 206A549 c 3,Header Font Color Data Producing Software 206A549 c 4, Header LocationData Producing Software 206A549 c 5, Document Header Displaying Software206A549 c 6, Document Data Transferring Software 206A549 c 7, HeaderText Data Transferring Software 206A549 c 8, Header Font Type DataTransferring Software 206A549 c 9, Header Font Size Data TransferringSoftware 206A549 c 10, Header Font Color Data Transferring Software206A549 c 11, Header Location Data Transferring Software 206A549 c 12,and Document Package Data Transferring Software 206A549 c 13. HeaderText Data Producing Software 206A549 c 1 is the software programdescribed hereinafter. Header Font Type Data Producing Software 206A549c 2 is the software program described hereinafter. Header Font Size DataProducing Software 206A549 c 3 is the software program describedhereinafter. Header Font Color Data Producing Software 206A549 c 4 isthe software program described hereinafter. Header Location DataProducing Software 206A549 c 5 is the software program describedhereinafter. Document Header Displaying Software 206A549 c 6 is thesoftware program described hereinafter. Document Data TransferringSoftware 206A549 c 7 is the software program described hereinafter.Header Text Data Transferring Software 206A549 c 8 is the softwareprogram described hereinafter. Header Font Type Data TransferringSoftware 206A549 c 9 is the software program described hereinafter.Header Font Size Data Transferring Software 206A549 c 10 is the softwareprogram described hereinafter. Header Font Color Data TransferringSoftware 206A549 c 11 is the software program described hereinafter.Header Location Data Transferring Software 206A549 c 12 is the softwareprogram described hereinafter. Document Package Data TransferringSoftware 206A549 c 13 is the software program described hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device B. In this embodiment, RAM 206 includes Header DisplayingInformation Storage Area 206B549 a of which the data and the softwareprogram(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device B.

This paragraph illustrates the storage area(s) included in HeaderDisplaying Information Storage Area 206B549 a. In this embodiment,Header Displaying Information Storage Area 206B549 a includes HeaderDisplaying Data Storage Area 206B549 b and Header Displaying SoftwareStorage Area 206B549 c. Header Displaying Data Storage Area 206B549 bstores the data necessary to implement the present function on the sideof Device B, such as the one(s) described hereinafter. Header DisplayingSoftware Storage Area 206B549 c stores the software program(s) necessaryto implement the present function on the side of Device B, such as theone(s) described hereinafter.

This paragraph illustrates the storage area(s) included in HeaderDisplaying Data Storage Area 206B549 b. In this embodiment, HeaderDisplaying Data Storage Area 206B549 b includes Document Data StorageArea 206B549 b 1, Header Preselected Data Storage Area 206B549 b 2, UserSelected Data Storage Area 206B549 b 3, and Work Area 206B549 b 4.Document Data Storage Area 206B549 b 1 stores the document data which isthe document capable to be displayed on LCD 201 (FIG. 1). The documentmay be the one which is produced by a word processing software (e.g., MSWord). Header Preselected Data Storage Area 206B549 b 2 stores the datadescribed hereinafter. User Selected Data Storage Area 206B549 b 3stores the data described hereinafter. Work Area 206B549 b 4 is utilizedas a work area to perform calculation and temporarily store data.

This paragraph illustrates the storage area(s) included in HeaderPreselected Data Storage Area 206B549 b 2. In this embodiment, HeaderPreselected Data Storage Area 206B549 b 2 includes Header PreselectedText Data Storage Area 206B549 b 2 a, Header Preselected Font Type DataStorage Area 206B549 b 2 b, Header Preselected Font Size Data StorageArea 206B549 b 2 c, Header Preselected Font Color Data Storage Area206B549 b 2 d, and Header Preselected Location Data Storage Area 206B549b 2 e. Header Preselected Text Data Storage Area 206B549 b 2 a storesthe data described hereinafter. Header Preselected Font Type DataStorage Area 206B549 b 2 b stores the data described hereinafter. HeaderPreselected Font Size Data Storage Area 206B549 b 2 c stores the datadescribed hereinafter. Header Preselected Font Color Data Storage Area206B549 b 2 d stores the data described hereinafter. Header PreselectedLocation Data Storage Area 206B549 b 2 e stores the data describedhereinafter.

This paragraph illustrates the data stored in Header Preselected TextData Storage Area 206B549 b 2 a. In this embodiment, Header PreselectedText Data Storage Area 206B549 b 2 a comprises two columns, i.e.,‘Header Preselected Text ID’ and ‘Header Preselected Text Data’. Column‘Header Preselected Text ID’ stores the header preselected text IDs, andeach header preselected text ID is an identification of thecorresponding header preselected text data stored in column ‘HeaderPreselected Text Data’. Each header preselected text ID may indicate thename or title of the corresponding header preselected text data. Column‘Header Preselected Text Data’ stores the header preselected text data,and each header preselected text data is the text data capable to beutilized as header of a document. In this embodiment, Header PreselectedText Data Storage Area 206B549 b 2 a stores the following data: ‘HeaderPreselected Text#1’ and the corresponding ‘Header Preselected TextData#1’; ‘Header Preselected Text#2’ and the corresponding HeaderPreselected Text Data#2; ‘Header Preselected Text#3’ and thecorresponding ‘Header Preselected Text Data#3’; and ‘Header PreselectedText#4’ and the corresponding ‘Header Preselected Text Data#4’.

This paragraph illustrates the data stored in Header Preselected FontType Data Storage Area 206B549 b 2 b. In this embodiment, HeaderPreselected Font Type Data Storage Area 206B549 b 2 b comprises twocolumns, i.e., ‘Header Preselected Font Type ID’ and ‘Header PreselectedFont Type Data’. Column ‘Header Preselected Font Type ID’ stores theheader preselected font type IDs, and each header preselected font typeID is an identification of the corresponding header preselected fonttype data stored in column ‘Header Preselected Font Type Data’. Eachheader preselected font type ID may indicate the name or title of thecorresponding header preselected font type data. Column ‘HeaderPreselected Font Type Data’ stores the header preselected font typedata, and each header preselected font type data indicates a specificfont type, such as Arial, Times New Roman, Tahoma, or Gothic. In thisembodiment, Header Preselected Font Type Data Storage Area 206B549 b 2 bstores the following data: ‘Header Preselected Font Type#1’ and thecorresponding ‘Header Preselected Font Type Data#1’; ‘Header PreselectedFont Type#2’ and the corresponding Header Preselected Font Type Data#2;‘Header Preselected Font Type#3’ and the corresponding ‘HeaderPreselected Font Type Data#3’; and ‘Header Preselected Font Type#4’ andthe corresponding ‘Header Preselected Font Type Data#4’.

This paragraph illustrates the data stored in Header Preselected FontSize Data Storage Area 206B549 b 2 c. In this embodiment, HeaderPreselected Font Size Data Storage Area 206B549 b 2 c comprises twocolumns, i.e., ‘Header Preselected Font Size ID’ and ‘Header PreselectedFont Size Data’. Column ‘Header Preselected Font Size ID’ stores theheader preselected font size IDs, and each header preselected font sizeID is an identification of the corresponding header preselected fontsize data stored in column ‘Header Preselected Font Size Data’. Eachheader preselected font size ID may indicate the name or title of thecorresponding header preselected font size data. Column ‘HeaderPreselected Font Size Data’ stores the header preselected font sizedata, and each header preselected font size data indicates a specificfont size, such as 8 points, 10 points, 14 points, or 18 points. In thisembodiment, Header Preselected Font Size Data Storage Area 206B549 b 2 cstores the following data: ‘Header Preselected Font Size 1’ and thecorresponding ‘Header Preselected Font Size Data#1’; ‘Header PreselectedFont Size#2’ and the corresponding ‘Header Preselected Font SizeData#2’; ‘Header Preselected Font Size#3’ and the corresponding ‘HeaderPreselected Font Size Data#3’; and ‘Header Preselected Font Size#4’ andthe corresponding ‘Header Preselected Font Size Data#4’.

This paragraph illustrates the data stored in Header Preselected FontColor Data Storage Area 206B549 b 2 d. In this embodiment, HeaderPreselected Font Color Data Storage Area 206B549 b 2 d comprises twocolumns, i.e., ‘Header Preselected Font Color ID’ and ‘HeaderPreselected Font Color Data’. Column ‘Header Preselected Font Color ID’stores the header preselected font color IDs, and each headerpreselected font color ID is an identification of the correspondingheader preselected font color data stored in column ‘Header PreselectedFont Color Data’. Each header preselected font color ID may indicate thename or title of the corresponding header preselected font color data.Column ‘Header Preselected Font Color Data’ stores the headerpreselected font color data, and each header preselected font color dataindicates a specific font color, such as red, blue, green or yellow. Inthis embodiment, Header Preselected Font Color Data Storage Area 206B549b 2 d stores the following data: ‘Header Preselected Font Color#1’ andthe corresponding ‘Header Preselected Font Color Data#1’; ‘HeaderPreselected Font Color#2’ and the corresponding ‘Header Preselected FontColor Data#2’; ‘Header Preselected Font Color#3’ and the corresponding‘Header Preselected Font Color Data#3’; and ‘Header Preselected FontColor#4’ and the corresponding ‘Header Preselected Font Color Data#4’.

This paragraph illustrates the data stored in Header PreselectedLocation Data Storage Area 206B549 b 2 e. In this embodiment, HeaderPreselected Location Data Storage Area 206B549 b 2 e comprises twocolumns, i.e., ‘Header Preselected Location ID’ and ‘Header PreselectedLocation Data’. Column ‘Header Preselected Location ID’ stores theheader preselected location IDs, and each header preselected location IDis an identification of the corresponding header preselected locationdata stored in column ‘Header Preselected Location Data’. Each headerpreselected location ID indicates the name or title of the correspondingheader preselected location data. Column ‘Header Preselected LocationData’ stores the header preselected location data, and each headerpreselected location data indicates the location at which the header isdisplayed in the document data. In this embodiment, Header PreselectedLocation Data Storage Area 206B549 b 2 e stores the following data:‘Header Preselected Location#1’ and the corresponding ‘HeaderPreselected Location Data#1’; ‘Header Preselected Location#2’ and thecorresponding ‘Header Preselected Location Data#2’; ‘Header PreselectedLocation#3’ and the corresponding ‘Header Preselected Location Data#3’;and ‘Header Preselected Location#4’ and the corresponding ‘HeaderPreselected Location Data#4’.

This paragraph illustrates the storage area(s) included in User SelectedData Storage Area 206B549 b 3. In this embodiment, User Selected DataStorage Area 206B549 b 3 includes Header Text Data Storage Area 206B549b 3 a, Header Font Type Data Storage Area 206B549 b 3 b, Header FontSize Data Storage Area 206B549 b 3 c, Header Font Color Data StorageArea 206B549 b 3 d, and Header Location Data Storage Area 206B549 b 3 e.Header Text Data Storage Area 206B549 b 3 a stores the header text datawhich is one of the header preselected text data selected by the user.Header Font Type Data Storage Area 206B549 b 3 b stores the header fonttype data which is one of the header preselected font type data selectedby the user. Header Font Size Data Storage Area 206B549 b 3 c stores theheader font size data which is one of the header preselected font sizedata selected by the user. Header Font Color Data Storage Area 206B549 b3 d stores the header font color data which is one of the headerpreselected font color data selected by the user. Header Location DataStorage Area 206B549 b 3 e stores the header location data which is oneof the header preselected location data selected by the user.

This paragraph illustrates the software program(s) stored in HeaderDisplaying Software Storage Area 206B549 c. In this embodiment, HeaderDisplaying Software Storage Area 206B549 c stores Document HeaderDisplaying Software 206B549 c 6, Document Data Transferring Software206B549 c 7, Header Text Data Transferring Software 206B549 c 8, HeaderFont Type Data Transferring Software 206B549 c 9, Header Font Size DataTransferring Software 206B549 c 10, Header Font Color Data TransferringSoftware 206B549 c 11, Header Location Data Transferring Software206B549 c 12, and Document Package Data Transferring Software 206B549 c13. Document Header Displaying Software 206B549 c 6 is the softwareprogram described hereinafter. Document Data Transferring Software206B549 c 7 is the software program described hereinafter. Header TextData Transferring Software 206B549 c 8 is the software program describedhereinafter. Header Font Type Data Transferring Software 206B549 c 9 isthe software program described hereinafter. Header Font Size DataTransferring Software 206B549 c 10 is the software program describedhereinafter. Header Font Color Data Transferring Software 206B549 c 11is the software program described hereinafter. Header Location DataTransferring Software 206B549 c 12 is the software program describedhereinafter. Document Package Data Transferring Software 206B549 c 13 isthe software program described hereinafter.

This paragraph illustrate(s) Header Text Data Producing Software H549 c1 of Host H and Header Text Data Producing Software 206A549 c 1 ofDevice A, which produce(s) the header text data. In this embodiment,Host H retrieves all header preselected text IDs (e.g., HeaderPreselected Text#1 through #4) from Header Preselected Text Data StorageArea H549 b 2 a and sends the data to Device A (S1). CPU 211 (FIG. 1) ofDevice A receives the header preselected text IDs (e.g., HeaderPreselected Text#1 through #4) from Host H in a wireless fashion anddisplays the data on LCD 201 (FIG. 1) of Device A (S2). The user ofDevice A selects, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, a header preselected text ID (e.g., HeaderPreselected Text#1) (S3). CPU 211 (FIG. 1) of Device A sends the headerpreselected text ID (e.g., Header Preselected Text#1) selected in theprevious step to Host H in a wireless fashion (S4). Host H receives theheader preselected text ID (e.g., Header Preselected Text#1) from DeviceA (S5). Host H retrieves the header preselected text data (e.g., HeaderPreselected Text Data#1) corresponding to the header preselected text ID(e.g., Header Preselected Text#1) received in the previous step fromHeader Preselected Text Data Storage Area H549 b 2 a (S6). Host H storesthe header preselected text data (e.g., Header Preselected Text Data#1)retrieved in the previous step as the header text data in Header TextData Storage Area H549 b 3 a (S7).

This paragraph illustrate(s) Header Font Type Data Producing SoftwareH549 c 2 of Host H and Header Font Type Data Producing Software 206A549c 2 of Device A, which produce(s) the header font type data. In thisembodiment, Host H retrieves all header preselected font type IDs (e.g.,Header Preselected Font Type#1 through #4) from Header Preselected FontType Data Storage Area H549 b 2 b and sends the data to Device A (S1).CPU 211 (FIG. 1) of Device A receives the header preselected font typeIDs (e.g., Header Preselected Font Type#1 through #4) from Host H in awireless fashion and displays the data on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a header preselected font typeID (e.g., Header Preselected Font Type#1) (S3). CPU 211 (FIG. 1) ofDevice A sends the header preselected font type ID (e.g., HeaderPreselected Font Type#1) selected in the previous step to Host H in awireless fashion (S4). Host H receives the header preselected font typeID (e.g., Header Preselected Font Type#1) from Device A (S5). Host Hretrieves the header preselected font type data (e.g., HeaderPreselected Font Type Data#1) corresponding to the header preselectedfont type ID (e.g., Header Preselected Font Type#1) received in theprevious step from Header Preselected Font Type Data Storage Area H549 b2 b (S6). Host H stores the header preselected font type data (e.g.,Header Preselected Font Type Data#1) retrieved in the previous step asthe header font type data in Header Font Type Data Storage Area H549 b 3b (S7).

This paragraph illustrate(s) Header Font Size Data Producing SoftwareH549 c 3 of Host H and Header Font Size Data Producing Software 206A549c 3 of Device A, which produce(s) the header font size data. In thisembodiment, Host H retrieves all header preselected font size IDs (e.g.,Header Preselected Font Size#1 through #4) from Header Preselected FontSize Data Storage Area H549 b 2 c and sends the data to Device A (S1).CPU 211 (FIG. 1) of Device A receives the header preselected font sizeIDs (e.g., Header Preselected Font Size#1 through #4) from Host H in awireless fashion and displays the data on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a header preselected font sizeID (e.g., Header Preselected Font Size#1) (S3). CPU 211 (FIG. 1) ofDevice A sends the header preselected font size ID (e.g., HeaderPreselected Font Size#1) selected in the previous step to Host H in awireless fashion (S4). Host H receives the header preselected font sizeID (e.g., Header Preselected Font Size#1) from Device A (S5). Host Hretrieves the header preselected font size data (e.g., HeaderPreselected Font Size Data#1) corresponding to the header preselectedfont size ID (e.g., Header Preselected Font Size#1) received in theprevious step from Header Preselected Font Size Data Storage Area H549 b2 c (S6). Host H stores the header preselected font size data (e.g.,Header Preselected Font Size Data#1) retrieved in the previous step asthe header font size data in Header Font Size Data Storage Area H549 b 3c (S7).

This paragraph illustrate(s) Header Font Color Data Producing SoftwareH549 c 4 of Host H and Header Font Color Data Producing Software 206A549c 4 of Device A, which produce(s) the header font color data. In thisembodiment, Host H retrieves all header preselected font color IDs(e.g., Header Preselected Font Color#1 through #4) from HeaderPreselected Font Color Data Storage Area H549 b 2 d and sends the datato Device A (S1). CPU 211 (FIG. 1) of Device A receives the headerpreselected font color IDs (e.g., Header Preselected Font Color#1through #4) from Host H in a wireless fashion and displays the data onLCD 201 (FIG. 1) of Device A (S2). The user of Device A selects, byutilizing Input Device 210 (FIG. 1) or via voice recognition system, aheader preselected font color ID (e.g., Header Preselected Font Color#1)(S3). CPU 211 (FIG. 1) of Device A sends the header preselected fontcolor ID (e.g., Header Preselected Font Color#1) selected in theprevious step to Host H in a wireless fashion (S4). Host H receives theheader preselected font color ID (e.g., Header Preselected Font Color#1)from Device A (S5). Host H retrieves the header preselected font colordata (e.g., Header Preselected Font Color Data#1) corresponding to theheader preselected font color ID (e.g., Header Preselected Font Color#1)received in the previous step from Header Preselected Font Color DataStorage Area H549 b 2 d (S6). Host H stores the header preselected fontcolor data (e.g., Header Preselected Font Color Data#1) retrieved in theprevious step as the header font color data in Header Font Color DataStorage Area H549 b 3 d (S7).

This paragraph illustrate(s) Header Location Data Producing SoftwareH549 c 5 of Host H and Header Location Data Producing Software 206A549 c5 of Device A, which produce(s) the header location data. In thisembodiment, Host H retrieves all header preselected location IDs (e.g.,Header Preselected Location#1 through #4) from Header PreselectedLocation Data Storage Area H549 b 2 e and sends the data to Device A(S1). CPU 211 (FIG. 1) of Device A receives the header preselectedlocation IDs (e.g., Header Preselected Location#1 through #4) from HostH in a wireless fashion and displays the data on LCD 201 (FIG. 1) ofDevice A (S2). The user of Device A selects, by utilizing Input Device210 (FIG. 1) or via voice recognition system, a header preselectedlocation ID (e.g., Header Preselected Location#1) (S3). CPU 211 (FIG. 1)of Device A sends the header preselected location ID (e.g., HeaderPreselected Location#1) selected in the previous step to Host H in awireless fashion (S4). Host H receives the header preselected locationID (e.g., Header Preselected Location#1) from Device A (S5). Host Hretrieves the header preselected location data (e.g., Header PreselectedLocation Data#1) corresponding to the header preselected location ID(e.g., Header Preselected Location#1) received in the previous step fromHeader Preselected Location Data Storage Area H549 b 2 e (S6). Host Hstores the header preselected location data (e.g., Header PreselectedLocation Data#1) retrieved in the previous step as the header locationdata in Header Location Data Storage Area H549 b 3 e (S7).

This paragraph illustrate(s) Document Header Displaying Software H549 c6 of Host H and Document Header Displaying Software 206A549 c 6 ofDevice A, which display(s) the header. In this embodiment, the user ofDevice A inputs, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, the document header displaying command (S1). Here,the document header displaying command is the command to display theheader. CPU 211 (FIG. 1) of Device A sends the document headerdisplaying command input in the previous step to Host H in a wirelessfashion (S2). Host H receives the document header displaying commandfrom Device A (S3). Host H retrieves the document data from DocumentData Storage Area H549 b 1 and sends the data to Device A (S4). CPU 211(FIG. 1) of Device A receives the document data from Host H in awireless fashion and stores the data in Document Data Storage Area206A549 b 1 (S5). Host H retrieves the header text data from Header TextData Storage Area H549 b 3 a and sends the data to Device A (S6). CPU211 (FIG. 1) of Device A receives the header text data from Host H in awireless fashion and stores the data in Header Text Data Storage Area206A549 b 3 a (S7). Host H retrieves the header font type data fromHeader Font Type Data Storage Area H549 b 3 b and sends the data toDevice A (S8). CPU 211 (FIG. 1) of Device A receives the header fonttype data from Host H in a wireless fashion and stores the data inHeader Font Type Data Storage Area 206A549 b 3 b (S9). Host H retrievesthe header font size data from Header Font Size Data Storage Area H549 b3 c and sends the data to Device A (S10). CPU 211 (FIG. 1) of Device Areceives the header font size data from Host H in a wireless fashion andstores the data in Header Font Size Data Storage Area 206A549 b 3 c(S11). Host H retrieves the header font color data from Header FontColor Data Storage Area H549 b 3 d and sends the data to Device A (S12).CPU 211 (FIG. 1) of Device A receives the header font color data fromHost H in a wireless fashion and stores the data in Header Font ColorData Storage Area 206A549 b 3 d (S13). Host H retrieves the headerlocation data from Header Location Data Storage Area H549 b 3 e andsends the data to Device A (S14). CPU 211 (FIG. 1) of Device A receivesthe header location data from Host H in a wireless fashion and storesthe data in Header Location Data Storage Area 206A549 b 3 e (S15). CPU211 (FIG. 1) of Device A retrieves the document data from Document DataStorage Area 206A549 b 1 (S16). CPU 211 (FIG. 1) of Device A displaysthe document data retrieved in the previous step on LCD 201 (FIG. 1) ofDevice A (S17). CPU 211 (FIG. 1) of Device A retrieves the header textdata from Header Text Data Storage Area 206A549 b 3 a (S18). CPU 211(FIG. 1) of Device A retrieves the header font type data from HeaderFont Type Data Storage Area 206A549 b 3 b (S19). CPU 211 (FIG. 1) ofDevice A retrieves the header font size data from Header Font Size DataStorage Area 206A549 b 3 c (S20). CPU 211 (FIG. 1) of Device A retrievesthe header font color data from Header Font Color Data Storage Area206A549 b 3 d (S21). CPU 211 (FIG. 1) of Device A retrieves the headerlocation data from Header Location Data Storage Area 206A549 b 3 e(S22). CPU 211 (FIG. 1) of Device A displays the header text dataretrieved in S18 in accordance with the header font type data retrievedin S19, Header Font Size Data retrieved in S20, and the header fontcolor data retrieved in S21 at the location indicated by the headerlocation data retrieved in S22 on Document Data displayed in S17 (S23).

This paragraph illustrate(s) Document Data Transferring Software H549 c7 of Host H, Document Data Transferring Software 206A549 c 7 of DeviceA, and Document Data Transferring Software 206B549 c 7 of Device B,which transfer(s) the document data. In this embodiment, the user ofDevice A inputs, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, the document data transferring command (S1). Here,the document data transferring command is the command to transfer thedocument data. CPU 211 (FIG. 1) of Device A sends the document datatransferring command input in the previous step to Host H in a wirelessfashion (S2). Host H receives the document data transferring commandfrom Device A (S3). Host H retrieves the document data from DocumentData Storage Area H549 b 1 and sends the data to Device B (S4). CPU 211(FIG. 1) of Device B receives the document data from Host H in awireless fashion and stores the data in Document Data Storage Area206B549 b 1 (S5).

This paragraph illustrate(s) Header Text Data Transferring Software H549c 8 of Host H, Header Text Data Transferring Software 206A549 c 8 ofDevice A, and Header Text Data Transferring Software 206B549 c 8 ofDevice B, which transfer(s) the header text data. In this embodiment,the user of Device A inputs, by utilizing Input Device 210 (FIG. 1) orvia voice recognition system, the header text data transferring command(S1). Here, the header text data transferring command is the command totransfer the header text data. CPU 211 (FIG. 1) of Device A sends theheader text data transferring command input in the previous step to HostH in a wireless fashion (S2). Host H receives the header text datatransferring command from Device A (S3). Host H retrieves the headertext data from Header Text Data Storage Area H549 b 3 a and sends thedata to Device B (S4). CPU 211 (FIG. 1) of Device B receives the headertext data from Host H in a wireless fashion and stores the data inHeader Text Data Storage Area 206B549 b 3 a (S5).

This paragraph illustrate(s) Header Font Type Data Transferring SoftwareH549 c 9 of Host H, Header Font Type Data Transferring Software 206A549c 9 of Device A, and Header Font Type Data Transferring Software 206B549c 9 of Device B, which transfer(s) the header font type data. In thisembodiment, the user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the header font type datatransferring command (S1). Here, the header font type data transferringcommand is the command to transfer the header font type data. CPU 211(FIG. 1) of Device A sends the header font type data transferringcommand input in the previous step to Host H in a wireless fashion (S2).Host H receives the header font type data transferring command fromDevice A (S3). Host H retrieves the header font type data from HeaderFont Type Data Storage Area H549 b 3 b and sends the data to Device B(S4). CPU 211 (FIG. 1) of Device B receives the header font type datafrom Host H in a wireless fashion and stores the data in Header FontType Data Storage Area 206B549 b 3 b (S5).

This paragraph illustrate(s) Header Font Size Data Transferring SoftwareH549 c 10 of Host H, Header Font Size Data Transferring Software 206A549c 10 of Device A, and Header Font Size Data Transferring Software206B549 c 10 of Device B, which transfer(s) the header font size data.In this embodiment, the user of Device A inputs, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, the header fontsize data transferring command (S1). Here, the header font size datatransferring command is the command to transfer the header font sizedata. CPU 211 (FIG. 1) of Device A sends the header font size datatransferring command input in the previous step to Host H in a wirelessfashion (S2). Host H receives the header font size data transferringcommand from Device A (S3). Host H retrieves the header font size datafrom Header Font Size Data Storage Area H549 b 3 c and sends the data toDevice B (S4). CPU 211 (FIG. 1) of Device B receives the header fontsize data from Host H in a wireless fashion and stores the data inHeader Font Size Data Storage Area 206B549 b 3 c (S5).

This paragraph illustrate(s) Header Font Color Data TransferringSoftware H549 c 11 of Host H, Header Font Color Data TransferringSoftware 206A549 c 11 of Device A, and Header Font Color DataTransferring Software 206B549 c 11 of Device B, which transfer(s) theheader font color data. In this embodiment, the user of Device A inputs,by utilizing Input Device 210 (FIG. 1) or via voice recognition system,the header font color data transferring command (S1). Here, the headerfont color data transferring command is the command to transfer theheader font color data. CPU 211 (FIG. 1) of Device A sends the headerfont color data transferring command input in the previous step to HostH in a wireless fashion (S2). Host H receives the header font color datatransferring command from Device A (S3). Host H retrieves the headerfont color data from Header Font Color Data Storage Area H549 b 3 d andsends the data to Device B (S4). CPU 211 (FIG. 1) of Device B receivesthe header font color data from Host H in a wireless fashion and storesthe data in Header Font Color Data Storage Area 206B549 b 3 d (S5).

This paragraph illustrate(s) Header Location Data Transferring SoftwareH549 c 12 of Host H, Header Location Data Transferring Software 206A549c 12 of Device A, and Header Location Data Transferring Software 206B549c 12 of Device B, which transfer(s) the header location data. In thisembodiment, the user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the header location datatransferring command (S1). Here, the header location data transferringcommand is the command to transfer the header location data. CPU 211(FIG. 1) of Device A sends the header location data transferring commandinput in the previous step to Host H in a wireless fashion (S2). Host Hreceives the header location data transferring command from Device A(S3). Host H retrieves the header location data from Header LocationData Storage Area H549 b 3 e and sends the data to Device B (S4). CPU211 (FIG. 1) of Device B receives the header location data from Host Hin a wireless fashion and stores the data in Header Location DataStorage Area 206B549 b 3 e (S5).

This paragraph illustrate(s) Document Package Data Transferring SoftwareH549 c 13 of Host H, Document Package Data Transferring Software 206A549c 13 of Device A, and Document Package Data Transferring Software206B549 c 13 of Device B, which transfer(s) the document data and allrelevant data. In this embodiment, the user of Device A inputs, byutilizing Input Device 210 (FIG. 1) or via voice recognition system, thedocument package data transferring command (S1). Here, the documentpackage data transferring command is the command to transfer thedocument data and all relevant data. CPU 211 (FIG. 1) of Device A sendsthe document package data transferring command to Host H in a wirelessfashion (S2). Host H receives the document package data transferringcommand from Device A (S3). Host H retrieves the document data fromDocument Data Storage Area H549 b 1 and sends the data to Device B in awireless fashion (S4). CPU 211 (FIG. 1) of Device B receives thedocument data from Host H in a wireless fashion and stores the data inDocument Data Storage Area 206B549 b 1 (S5). Host H retrieves the headertext data from Header Text Data Storage Area H549 b 3 a and sends thedata to Device B in a wireless fashion (S6). CPU 211 (FIG. 1) of DeviceB receives the header text data from Host H in a wireless fashion andstores the data in Header Text Data Storage Area 206B549 b 3 a (S7).Host H retrieves the header font type data from Header Font Type DataStorage Area H549 b 3 b and sends the data to Device B in a wirelessfashion (S8). CPU 211 (FIG. 1) of Device B receives the header font typedata from Host H in a wireless fashion and stores the data in HeaderFont Type Data Storage Area 206B549 b 3 b (S9). Host H retrieves theheader font size data from Header Font Size Data Storage Area H549 b 3 cand sends the data to Device B in a wireless fashion (S10). CPU 211(FIG. 1) of Device B receives the header font size data from Host H in awireless fashion and stores the data in Header Font Size Data StorageArea 206B549 b 3 c (S11). Host H retrieves the header font color datafrom Header Font Color Data Storage Area H549 b 3 d and sends the datato Device B in a wireless fashion (S12). CPU 211 (FIG. 1) of Device Breceives the header font color data from Host H in a wireless fashionand stores the data in Header Font Color Data Storage Area 206B549 b 3 d(S13). Host H retrieves the header location data from Header LocationData Storage Area H549 b 3 e and sends the data to Device B in awireless fashion (S14). CPU 211 (FIG. 1) of Device B receives the headerlocation data from Host H in a wireless fashion and stores the data inHeader Location Data Storage Area 206B549 b 3 e (S15).

This paragraph illustrate(s) Document Header Displaying Software 206B549c 6 of Device B, which display(s) the header. In this embodiment, theuser of Device B inputs, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, the document header displaying command (S1).Here, the document header displaying command is the command to displaythe header. CPU 211 (FIG. 1) of Device B retrieves the document datafrom Document Data Storage Area 206B549 b 1 (S2). CPU 211 (FIG. 1) ofDevice B displays the document data retrieved in the previous step onLCD 201 (FIG. 1) of Device B (S3). CPU 211 (FIG. 1) of Device Bretrieves the header text data from Header Text Data Storage Area206B549 b 3 a (S4). CPU 211 (FIG. 1) of Device B retrieves the headerfont type data from Header Font Type Data Storage Area 206B549 b 3 b(S5). CPU 211 (FIG. 1) of Device B retrieves the header font size datafrom Header Font Size Data Storage Area 206B549 b 3 c (S6). CPU 211(FIG. 1) of Device B retrieves the header font color data from HeaderFont Color Data Storage Area 206B549 b 3 d (S7). CPU 211 (FIG. 1) ofDevice B retrieves the header location data from Header Location DataStorage Area 206B549 b 3 e (S8). CPU 211 (FIG. 1) of Device B displaysthe header text data retrieved in S4 in accordance with the header fonttype data retrieved in S5, Header Font Size Data retrieved in S6, andthe header font color data retrieved in S7 at the location indicated bythe header location data retrieved in S8 on Document Data displayed inS3 (S9).

The following paragraphs illustrate another embodiment wherein Device Aplays the major role in implementing the present function.

This paragraph illustrate(s) Header Text Data Producing Software 206A549c 1 of Device A, which produce(s) the header text data. In thisembodiment, CPU 211 (FIG. 1) of Device A retrieves all headerpreselected text IDs (e.g., Header Preselected Text#1 through #4) fromHeader Preselected Text Data Storage Area 206A549 b 2 a (S1). CPU 211(FIG. 1) of Device A displays the header preselected text IDs (e.g.,Header Preselected Text#1 through #4) retrieved in the previous step onLCD 201 (FIG. 1) of Device A (S2). The user of Device A selects, byutilizing Input Device 210 (FIG. 1) or via voice recognition system, aheader preselected text ID (e.g., Header Preselected Text#1) (S3). CPU211 (FIG. 1) of Device A retrieves the header preselected text data(e.g., Header Preselected Text Data#1) corresponding to the headerpreselected text ID (e.g., Header Preselected Text#1) selected in theprevious step from Header Preselected Text Data Storage Area 206A549 b 2a (S4). CPU 211 (FIG. 1) of Device A stores the header preselected textdata (e.g., Header Preselected Text Data#1) retrieved in the previousstep as the header text data in Header Text Data Storage Area 206A549 b3 a (S5).

This paragraph illustrate(s) Header Font Type Data Producing Software206A549 c 2 of Device A, which produce(s) the header font type data. Inthis embodiment, CPU 211 (FIG. 1) of Device A retrieves all headerpreselected font type IDs (e.g., Header Preselected Font Type#1 through#4) from Header Preselected Font Type Data Storage Area 206A549 b 2 b(S1). CPU 211 (FIG. 1) of Device A displays the header preselected fonttype IDs (e.g., Header Preselected Font Type#1 through #4) retrieved inthe previous step on LCD 201 (FIG. 1) of Device A (S2). The user ofDevice A selects, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, a header preselected font type ID (e.g., HeaderPreselected Font Type#1) (S3). CPU 211 (FIG. 1) of Device A retrievesthe header preselected font type data (e.g., Header Preselected FontType Data#1) corresponding to the header preselected font type ID (e.g.,Header Preselected Font Type#1) selected in the previous step fromHeader Preselected Font Type Data Storage Area 206A549 b 2 b (S4). CPU211 (FIG. 1) of Device A stores the header preselected font type data(e.g., Header Preselected Font Type Data#1) retrieved in the previousstep as the header font type data in Header Font Type Data Storage Area206A549 b 3 b (S5).

This paragraph illustrate(s) Header Font Size Data Producing Software206A549 c 3 of Device A, which produce(s) the header font size data. Inthis embodiment, CPU 211 (FIG. 1) of Device A retrieves all headerpreselected font size IDs (e.g., Header Preselected Font Size#1 through#4) from Header Preselected Font Size Data Storage Area 206A549 b 2 c(S1). CPU 211 (FIG. 1) of Device A displays the header preselected fontsize IDs (e.g., Header Preselected Font Size#1 through #4) retrieved inthe previous step on LCD 201 (FIG. 1) of Device A (S2). The user ofDevice A selects, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, a header preselected font size ID (e.g., HeaderPreselected Font Size#1) (S3). CPU 211 (FIG. 1) of Device A retrievesthe header preselected font size data (e.g., Header Preselected FontSize Data#1) corresponding to the header preselected font size ID (e.g.,Header Preselected Font Size#1) selected in the previous step fromHeader Preselected Font Size Data Storage Area 206A549 b 2 c (S4). CPU211 (FIG. 1) of Device A stores the header preselected font size data(e.g., Header Preselected Font Size Data#1) retrieved in the previousstep as the header font size data in Header Font Size Data Storage Area206A549 b 3 c (S5).

This paragraph illustrate(s) Header Font Color Data Producing Software206A549 c 4 of Device A, which produce(s) the header font color data. Inthis embodiment, CPU 211 (FIG. 1) of Device A retrieves all headerpreselected font color IDs (e.g., Header Preselected Font Color#1through #4) from Header Preselected Font Color Data Storage Area 206A549b 2 d (S1). CPU 211 (FIG. 1) of Device A displays the header preselectedfont color IDs (e.g., Header Preselected Font Color#1 through #4)retrieved in the previous step on LCD 201 (FIG. 1) of Device A (S2). Theuser of Device A selects, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, a header preselected font color ID (e.g.,Header Preselected Font Color#1) (S3). CPU 211 (FIG. 1) of Device Aretrieves the header preselected font color data (e.g., HeaderPreselected Font Color Data#1) corresponding to the header preselectedfont color ID (e.g., Header Preselected Font Color#1) selected in theprevious step from Header Preselected Font Color Data Storage Area206A549 b 2 d (S4). CPU 211 (FIG. 1) of Device A stores the headerpreselected font color data (e.g., Header Preselected Font Color Data#1)retrieved in the previous step as the header font color data in HeaderFont Color Data Storage Area 206A549 b 3 d (S5).

This paragraph illustrate(s) Header Location Data Producing Software206A549 c 5 of Device A, which produce(s) the header location data. Inthis embodiment, CPU 211 (FIG. 1) of Device A retrieves all headerpreselected location IDs (e.g., Header Preselected Location#1 through#4) from Header Preselected Location Data Storage Area 206A549 b 2 e(S1). CPU 211 (FIG. 1) of Device A displays the header preselectedlocation IDs (e.g., Header Preselected Location#1 through #4) retrievedin the previous step on LCD 201 (FIG. 1) of Device A (S2). The user ofDevice A selects, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, a header preselected location ID (e.g., HeaderPreselected Location#1) (S3). CPU 211 (FIG. 1) of Device A retrieves theheader preselected location data (e.g., Header Preselected LocationData#1) corresponding to the header preselected location ID (e.g.,Header Preselected Location#1) selected in the previous step from HeaderPreselected Location Data Storage Area 206A549 b 2 e (S4). CPU 211(FIG. 1) of Device A stores the header preselected location data (e.g.,Header Preselected Location Data#1) retrieved in the previous step asthe header location data in Header Location Data Storage Area 206A549 b3 e (S5).

This paragraph illustrate(s) Document Header Displaying Software 206A549c 6 of Device A, which display(s) the header. In this embodiment, theuser of Device A inputs, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, the document header displaying command (S1).Here, the document header displaying command is the command to displaythe header. CPU 211 (FIG. 1) of Device A retrieves the document datafrom Document Data Storage Area 206A549 b 1 (S2). CPU 211 (FIG. 1) ofDevice A displays the document data retrieved in the previous step onLCD 201 (FIG. 1) of Device A (S3). CPU 211 (FIG. 1) of Device Aretrieves the header text data from Header Text Data Storage Area206A549 b 3 a (S4). CPU 211 (FIG. 1) of Device A retrieves the headerfont type data from Header Font Type Data Storage Area 206A549 b 3 b(S5). CPU 211 (FIG. 1) of Device A retrieves the header font size datafrom Header Font Size Data Storage Area 206A549 b 3 c (S6). CPU 211(FIG. 1) of Device A retrieves the header font color data from HeaderFont Color Data Storage Area 206A549 b 3 d (S7). CPU 211 (FIG. 1) ofDevice A retrieves the header location data from Header Location DataStorage Area 206A549 b 3 e (S8). CPU 211 (FIG. 1) of Device A displaysthe header text data retrieved in S4 in accordance with the header fonttype data retrieved in S5, Header Font Size Data retrieved in S6, andthe header font color data retrieved in S7 at the location indicated bythe header location data retrieved in S8 on Document Data displayed inS3 (S9).

This paragraph illustrate(s) Document Data Transferring Software 206A549c 7 of Device A and Document Data Transferring Software 206B549 c 7 ofDevice B, which transfer(s) the document data. In this embodiment, theuser of Device A inputs, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, the document data transferring command (S1).Here, the document data transferring command is the command to transferthe document data. CPU 211 (FIG. 1) of Device A retrieves the documentdata from Document Data Storage Area 206A549 b 1 and sends the data toDevice B in a wireless fashion (S2). CPU 211 (FIG. 1) of Device Breceives the document data from Device A in a wireless fashion andstores the data in Document Data Storage Area 206B549 b 1 (S3).

This paragraph illustrate(s) Header Text Data Transferring Software206A549 c 8 of Device A and Header Text Data Transferring Software206B549 c 8 of Device B, which transfer(s) the header text data. In thisembodiment, the user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the header text datatransferring command (S1). Here, the header text data transferringcommand is the command to transfer the header text data. CPU 211(FIG. 1) of Device A retrieves the header text data from Header TextData Storage Area 206A549 b 3 a and sends the data to Device B in awireless fashion (S2). CPU 211 (FIG. 1) of Device B receives the headertext data from Device A in a wireless fashion and stores the data inHeader Text Data Storage Area 206B549 b 3 a (S3).

This paragraph illustrate(s) Header Font Type Data Transferring Software206A549 c 9 of Device A and Header Font Type Data Transferring Software206B549 c 9 of Device B, which transfer(s) the header font type data. Inthis embodiment, the user of Device A inputs, by utilizing Input Device210 (FIG. 1) or via voice recognition system, the header font type datatransferring command (S1). Here, the header font type data transferringcommand is the command to transfer the header font type data. CPU 211(FIG. 1) of Device A retrieves the header font type data from HeaderFont Type Data Storage Area 206A549 b 3 b and sends the data to Device Bin a wireless fashion (S2). CPU 211 (FIG. 1) of Device B receives theheader font type data from Device A in a wireless fashion and stores thedata in Header Font Type Data Storage Area 206B549 b 3 b (S3).

This paragraph illustrate(s) Header Font Size Data Transferring Software206A549 c 10 of Device A and Header Font Size Data Transferring Software206B549 c 10 of Device B, which transfer(s) the header font size data.In this embodiment, the user of Device A inputs, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, the header fontsize data transferring command (S1). Here, the header font size datatransferring command is the command to transfer the header font sizedata. CPU 211 (FIG. 1) of Device A retrieves the header font size datafrom Header Font Size Data Storage Area 206A549 b 3 c and sends the datato Device B in a wireless fashion (S2). CPU 211 (FIG. 1) of Device Breceives the header font size data from Device A in a wireless fashionand stores the data in Header Font Size Data Storage Area 206B549 b 3 c(S3).

This paragraph illustrate(s) Header Font Color Data TransferringSoftware 206A549 c 11 of Device A and Header Font Color DataTransferring Software 206B549 c 11 of Device B, which transfer(s) theheader font color data. In this embodiment, the user of Device A inputs,by utilizing Input Device 210 (FIG. 1) or via voice recognition system,the header font color data transferring command (S1). Here, the headerfont color data transferring command is the command to transfer theheader font color data. CPU 211 (FIG. 1) of Device A retrieves theheader font color data from Header Font Color Data Storage Area 206A549b 3 d and sends the data to Device B in a wireless fashion (S2). CPU 211(FIG. 1) of Device B receives the header font color data from Device Ain a wireless fashion and stores the data in Header Font Color DataStorage Area 206B549 b 3 d (S3).

This paragraph illustrate(s) Header Location Data Transferring Software206A549 c 12 of Device A and Header Location Data Transferring Software206B549 c 12 of Device B, which transfer(s) the header location data. Inthis embodiment, the user of Device A inputs, by utilizing Input Device210 (FIG. 1) or via voice recognition system, the header location datatransferring command (S1). Here, the header location data transferringcommand is the command to transfer the header location data. CPU 211(FIG. 1) of Device A retrieves the header location data from HeaderLocation Data Storage Area 206A549 b 3 e and sends the data to Device Bin a wireless fashion (S2). CPU 211 (FIG. 1) of Device B receives theheader location data from Device A in a wireless fashion and stores thedata in Header Location Data Storage Area 206B549 b 3 e (S3).

This paragraph illustrate(s) Document Package Data Transferring Software206A549 c 13 of Device A and Document Package Data Transferring Software206B549 c 13 of Device B, which transfer(s) the document data and allrelevant data. In this embodiment, the user of Device A inputs, byutilizing Input Device 210 (FIG. 1) or via voice recognition system, thedocument package data transferring command (S1). Here, the documentpackage data transferring command is the command to transfer thedocument data and all relevant data. CPU 211 (FIG. 1) of Device Aretrieves the document data from Document Data Storage Area 206A549 b 1and sends the data to Device B in a wireless fashion (S2). CPU 211(FIG. 1) of Device B receives the document data from Device A in awireless fashion and stores the data in Document Data Storage Area206B549 b 1 (S3). CPU 211 (FIG. 1) of Device A retrieves the header textdata from Header Text Data Storage Area 206A549 b 3 a and sends the datato Device B in a wireless fashion (S4). CPU 211 (FIG. 1) of Device Breceives the header text data from Device A in a wireless fashion andstores the data in Header Text Data Storage Area 206B549 b 3 a (S5). CPU211 (FIG. 1) of Device A retrieves the header font type data from HeaderFont Type Data Storage Area 206A549 b 3 b and sends the data to Device Bin a wireless fashion (S6). CPU 211 (FIG. 1) of Device B receives theheader font type data from Device A in a wireless fashion and stores thedata in Header Font Type Data Storage Area 206B549 b 3 b (S7). CPU 211(FIG. 1) of Device A retrieves the header font size data from HeaderFont Size Data Storage Area 206A549 b 3 c and sends the data to Device Bin a wireless fashion (S 8). CPU 211 (FIG. 1) of Device B receives theheader font size data from Device A in a wireless fashion and stores thedata in Header Font Size Data Storage Area 206B549 b 3 c (S9). CPU 211(FIG. 1) of Device A retrieves the header font color data from HeaderFont Color Data Storage Area 206A549 b 3 d and sends the data to DeviceB in a wireless fashion (S10). CPU 211 (FIG. 1) of Device B receives theheader font color data from Device A in a wireless fashion and storesthe data in Header Font Color Data Storage Area 206B549 b 3 d (S11). CPU211 (FIG. 1) of Device A retrieves the header location data from HeaderLocation Data Storage Area 206A549 b 3 e and sends the data to Device Bin a wireless fashion (S12). CPU 211 (FIG. 1) of Device B receives theheader location data from Device A in a wireless fashion and stores thedata in Header Location Data Storage Area 206B549 b 3 e (S13).

This paragraph illustrate(s) Document Header Displaying Software 206B549c 6 of Device B, which display(s) the header. In this embodiment, theuser of Device B inputs, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, the document header displaying command (S1).Here, the document header displaying command is the command to displaythe header. CPU 211 (FIG. 1) of Device B retrieves the document datafrom Document Data Storage Area 206B549 b 1 (S2). CPU 211 (FIG. 1) ofDevice B displays the document data retrieved in the previous step onLCD 201 (FIG. 1) of Device B (S3). CPU 211 (FIG. 1) of Device Bretrieves the header text data from Header Text Data Storage Area206B549 b 3 a (S4). CPU 211 (FIG. 1) of Device B retrieves the headerfont type data from Header Font Type Data Storage Area 206B549 b 3 b(S5). CPU 211 (FIG. 1) of Device B retrieves the header font size datafrom Header Font Size Data Storage Area 206B549 b 3 c (S6). CPU 211(FIG. 1) of Device B retrieves the header font color data from HeaderFont Color Data Storage Area 206B549 b 3 d (S7). CPU 211 (FIG. 1) ofDevice B retrieves the header location data from Header Location DataStorage Area 206B549 b 3 e (S8). CPU 211 (FIG. 1) of Device B displaysthe header text data retrieved in S4 in accordance with the header fonttype data retrieved in S5, Header Font Size Data retrieved in S6, andthe header font color data retrieved in S7 at the location indicated bythe header location data retrieved in S8 on Document Data displayed inS3 (S9).

<<Footer Displaying Function>>

The following paragraphs illustrate the footer displaying function,wherein when a document is displayed on LCD 201 (FIG. 1), the footer isdisplayed in the document. The text of the footer is identified byCommunication Device 200. The font type of the footer is identified byCommunication Device 200. The font size of the footer is identified byCommunication Device 200. The font color of the footer is identified byCommunication Device 200. The location of the footer displayed in thedocument is identified by Communication Device 200. The document and thetext, font type, font size, font color, and location of the footer aretransferred to another device, and the another device displays thedocument with the footer in accordance with the text, font type, fontsize, font color, and location received. Here, the footer (or thedocument footer) is the common text displayed at the lower portion ofeach page of a document. The footer may indicate the page number of thecorresponding page of the document.

This paragraph illustrates the major elements utilized to implement thepresent function. In this embodiment, Host H is connected to Network NT(e.g., the Internet). Device A, a Communication Device 200, is connectedto Network NT (e.g., the Internet) in a wireless fashion. Device B,another Communication Device 200, is connected to Network NT (e.g., theInternet) in a wireless fashion. Host H, Device A, and Device B arecapable to communicate with each other via Network NT (e.g., theInternet) to implement the present function. Device A and Device B arealso capable to communicate with each other directly in a wirelessfashion to implement the present function.

This paragraph illustrates the storage area included in Host H. In thisembodiment, Host H includes Footer Displaying Information Storage AreaH550 a of which the data and the software program(s) stored therein aredescribed hereinafter.

This paragraph illustrates the storage area(s) included in FooterDisplaying Information Storage Area H550 a. In this embodiment, FooterDisplaying Information Storage Area H550 a includes Footer DisplayingData Storage Area H550 b and Footer Displaying Software Storage AreaH550 c. Footer Displaying Data Storage Area H550 b stores the datanecessary to implement the present function on the side of Host H, suchas the one(s) described hereinafter. Footer Displaying Software StorageArea H550 c stores the software program(s) necessary to implement thepresent function on the side of Host H, such as the one(s) describedhereinafter.

This paragraph illustrates the storage area(s) included in FooterDisplaying Data Storage Area H550 b. In this embodiment, FooterDisplaying Data Storage Area H550 b includes Document Data Storage AreaH550 b 1, Footer Preselected Data Storage Area H550 b 2, User SelectedData Storage Area H550 b 3, and Work Area H550 b 4. Document DataStorage Area H550 b 1 stores the document data which is the documentcapable to be displayed on LCD 201 (FIG. 1). The document may be the onewhich is produced by a word processing software (e.g., MS Word). FooterPreselected Data Storage Area H550 b 2 stores the data describedhereinafter. User Selected Data Storage Area H550 b 3 stores the datadescribed hereinafter. Work Area H550 b 4 is utilized as a work area toperform calculation and temporarily store data.

This paragraph illustrates the storage area(s) included in FooterPreselected Data Storage Area H550 b 2. In this embodiment, FooterPreselected Data Storage Area H550 b 2 includes Footer Preselected TextData Storage Area H550 b 2 a, Footer Preselected Font Type Data StorageArea H550 b 2 b, Footer Preselected Font Size Data Storage Area H550 b 2c, Footer Preselected Font Color Data Storage Area H550 b 2 d, andFooter Preselected Location Data Storage Area H550 b 2 e. FooterPreselected Text Data Storage Area H550 b 2 a stores the data describedhereinafter. Footer Preselected Font Type Data Storage Area H550 b 2 bstores the data described hereinafter. Footer Preselected Font Size DataStorage Area H550 b 2 c stores the data described hereinafter. FooterPreselected Font Color Data Storage Area H550 b 2 d stores the datadescribed hereinafter. Footer Preselected Location Data Storage AreaH550 b 2 e stores the data described hereinafter.

This paragraph illustrates the data stored in Footer Preselected TextData Storage Area H550 b 2 a. In this embodiment, Footer PreselectedText Data Storage Area H550 b 2 a comprises two columns, i.e., ‘FooterPreselected Text ID’ and ‘Footer Preselected Text Data’. Column ‘FooterPreselected Text ID’ stores the footer preselected text IDs, and eachfooter preselected text ID is an identification of the correspondingfooter preselected text data stored in column ‘Footer Preselected TextData’. Each footer preselected text ID may indicate the name or title ofthe corresponding footer preselected text data. Column ‘FooterPreselected Text Data’ stores the footer preselected text data, and eachfooter preselected text data is the text data capable to be utilized asfooter of a document. In this embodiment, Footer Preselected Text DataStorage Area H550 b 2 a stores the following data: Footer PreselectedText#1’ and the corresponding ‘Footer Preselected Text Data#1’; FooterPreselected Text#2’ and the corresponding ‘Footer Preselected TextData#2’; Footer Preselected Text#3’ and the corresponding ‘FooterPreselected Text Data#3’; and Footer Preselected Text#4’ and thecorresponding ‘Footer Preselected Text Data#4’.

This paragraph illustrates the data stored in Footer Preselected FontType Data Storage Area H550 b 2 b. In this embodiment, FooterPreselected Font Type Data Storage Area H550 b 2 b comprises twocolumns, i.e., ‘Footer Preselected Font Type ID’ and ‘Footer PreselectedFont Type Data’. Column ‘Footer Preselected Font Type ID’ stores thefooter preselected font type IDs, and each footer preselected font typeID is an identification of the corresponding footer preselected fonttype data stored in column ‘Footer Preselected Font Type Data’. Eachfooter preselected font type ID may indicate the name or title of thecorresponding footer preselected font type data. Column ‘FooterPreselected Font Type Data’ stores the footer preselected font typedata, and each footer preselected font type data indicates a specificfont type, such as Arial, Times New Roman, Tahoma, or Gothic. In thisembodiment, Footer Preselected Font Type Data Storage Area H550 b 2 bstores the following data: Footer Preselected Font Type#1’ and thecorresponding ‘Footer Preselected Font Type Data#1’; Footer PreselectedFont Type#2’ and the corresponding ‘Footer Preselected Font Type Data#2;Footer Preselected Font Type#3’ and the corresponding ‘FooterPreselected Font Type Data#3’; and Footer Preselected Font Type#4’ andthe corresponding ‘Footer Preselected Font Type Data#4’.

This paragraph illustrates the data stored in Footer Preselected FontSize Data Storage Area H550 b 2 c. In this embodiment, FooterPreselected Font Size Data Storage Area H550 b 2 c comprises twocolumns, i.e., ‘Footer Preselected Font Size ID’ and ‘Footer PreselectedFont Size Data’. Column ‘Footer Preselected Font Size ID’ stores thefooter preselected font size IDs, and each footer preselected font sizeID is an identification of the corresponding footer preselected fontsize data stored in column ‘Footer Preselected Font Size Data’. Eachfooter preselected font size ID may indicate the name or title of thecorresponding footer preselected font size data. Column ‘FooterPreselected Font Size Data’ stores the footer preselected font sizedata, and each footer preselected font size data indicates a specificfont size, such as 8 points, 10 points, 14 points, or 18 points. In thisembodiment, Footer Preselected Font Size Data Storage Area H550 b 2 cstores the following data: Footer Preselected Font Size#1’ and thecorresponding ‘Footer Preselected Font Size Data#1’; Footer PreselectedFont Size#2’ and the corresponding ‘Footer Preselected Font Size Data#2;Footer Preselected Font Size#3’ and the corresponding ‘FooterPreselected Font Size Data#3’; and Footer Preselected Font Size#4’ andthe corresponding ‘Footer Preselected Font Size Data#4’.

This paragraph illustrates the data stored in Footer Preselected FontColor Data Storage Area H550 b 2 d. In this embodiment, FooterPreselected Font Color Data Storage Area H550 b 2 d comprises twocolumns, i.e., ‘Footer Preselected Font Color ID’ and ‘FooterPreselected Font Color Data’. Column ‘Footer Preselected Font Color ID’stores the footer preselected font color IDs, and each footerpreselected font color ID is an identification of the correspondingfooter preselected font color data stored in column ‘Footer PreselectedFont Color Data’. Each footer preselected font color ID may indicate thename or title of the corresponding footer preselected font color data.Column ‘Footer Preselected Font Color Data’ stores the footerpreselected font color data, and each footer preselected font color dataindicates a specific font color, such as red, blue, green or yellow. Inthis embodiment, Footer Preselected Font Color Data Storage Area H550 b2 d stores the following data: Footer Preselected Font Color#1’ and thecorresponding ‘Footer Preselected Font Color Data#1’; Footer PreselectedFont Color#2’ and the corresponding ‘Footer Preselected Font ColorData#2; Footer Preselected Font Color#3’ and the corresponding ‘FooterPreselected Font Color Data#3’; and Footer Preselected Font Color#4’ andthe corresponding ‘Footer Preselected Font Color Data#4’.

This paragraph illustrates the data stored in Footer PreselectedLocation Data Storage Area H550 b 2 e. In this embodiment, FooterPreselected Location Data Storage Area H550 b 2 e comprises two columns,i.e., ‘Footer Preselected Location ID’ and ‘Footer Preselected LocationData’. Column ‘Footer Preselected Location ID’ stores the footerpreselected location IDs, and each footer preselected location ID is anidentification of the corresponding footer preselected location datastored in column ‘Footer Preselected Location Data’. Each footerpreselected location ID indicates the name or title of the correspondingfooter preselected location data. Column ‘Footer Preselected LocationData’ stores the footer preselected location data, and each footerpreselected location data indicates the location at which the footer isdisplayed in the document data. In this embodiment, Footer PreselectedLocation Data Storage Area H550 b 2 e stores the following data: FooterPreselected Location#1’ and the corresponding ‘Footer PreselectedLocation Data#1’; Footer Preselected Location#2’ and the corresponding‘Footer Preselected Location Data#2’; Footer Preselected Location#3’ andthe corresponding ‘Footer Preselected Location Data#3’; and FooterPreselected Location#4’ and the corresponding ‘Footer PreselectedLocation Data#4’.

This paragraph illustrates the storage area(s) included in User SelectedData Storage Area H550 b 3. In this embodiment, User Selected DataStorage Area H550 b 3 includes Footer Text Data Storage Area H550 b 3 a,Footer Font Type Data Storage Area H550 b 3 b, Footer Font Size DataStorage Area H550 b 3 c, Footer Font Color Data Storage Area H550 b 3 d,and Footer Location Data Storage Area H550 b 3 e. Footer Text DataStorage Area H550 b 3 a stores the footer text data which is one of thefooter preselected text data selected by the user. Footer Font Type DataStorage Area H550 b 3 b stores the footer font type data which is one ofthe footer preselected font type data selected by the user. Footer FontSize Data Storage Area H550 b 3 c stores the footer font size data whichis one of the footer preselected font size data selected by the user.Footer Font Color Data Storage Area H550 b 3 d stores the footer fontcolor data which is one of the footer preselected font color dataselected by the user. Footer Location Data Storage Area H550 b 3 estores the footer location data which is one of the footer preselectedlocation data selected by the user.

This paragraph illustrates the software program(s) stored in FooterDisplaying Software Storage Area H550 c. In this embodiment, FooterDisplaying Software Storage Area H550 c stores Footer Text DataProducing Software H550 c 1, Footer Font Type Data Producing SoftwareH550 c 2, Footer Font Size Data Producing Software H550 c 3, Footer FontColor Data Producing Software H550 c 4, Footer Location Data ProducingSoftware H550 c 5, Document Footer Displaying Software H550 c 6,Document Data Transferring Software H550 c 7, Footer Text DataTransferring Software H550 c 8, Footer Font Type Data TransferringSoftware H550 c 9, Footer Font Size Data Transferring Software H550 c10, Footer Font Color Data Transferring Software H550 c 11, FooterLocation Data Transferring Software H550 c 12, and Document Package DataTransferring Software H550 c 13. Footer Text Data Producing SoftwareH550 c 1 is the software program described hereinafter. Footer Font TypeData Producing Software H550 c 2 is the software program describedhereinafter. Footer Font Size Data Producing Software H550 c 3 is thesoftware program described hereinafter. Footer Font Color Data ProducingSoftware H550 c 4 is the software program described hereinafter. FooterLocation Data Producing Software H550 c 5 is the software programdescribed hereinafter. Document Footer Displaying Software H550 c 6 isthe software program described hereinafter. Document Data TransferringSoftware H550 c 7 is the software program described hereinafter. FooterText Data Transferring Software H550 c 8 is the software programdescribed hereinafter. Footer Font Type Data Transferring Software H550c 9 is the software program described hereinafter. Footer Font Size DataTransferring Software H550 c 10 is the software program describedhereinafter. Footer Font Color Data Transferring Software H550 c 11 isthe software program described hereinafter. Footer Location DataTransferring Software H550 c 12 is the software program describedhereinafter. Document Package Data Transferring Software H550 c 13 isthe software program described hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device A. In this embodiment, RAM 206 includes Footer DisplayingInformation Storage Area 206A550 a of which the data and the softwareprogram(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device A.

This paragraph illustrates the storage area(s) included in FooterDisplaying Information Storage Area 206A550 a. In this embodiment,Footer Displaying Information Storage Area 206A550 a includes FooterDisplaying Data Storage Area 206A550 b and Footer Displaying SoftwareStorage Area 206A550 c. Footer Displaying Data Storage Area 206A550 bstores the data necessary to implement the present function on the sideof Device A, such as the one(s) described hereinafter. Footer DisplayingSoftware Storage Area 206A550 c stores the software program(s) necessaryto implement the present function on the side of Device A, such as theone(s) described hereinafter.

This paragraph illustrates the storage area(s) included in FooterDisplaying Data Storage Area 206A550 b. In this embodiment, FooterDisplaying Data Storage Area 206A550 b includes Document Data StorageArea 206A550 b 1, Footer Preselected Data Storage Area 206A550 b 2, UserSelected Data Storage Area 206A550 b 3, and Work Area 206A550 b 4.Document Data Storage Area 206A550 b 1 stores the document data which isthe document capable to be displayed on LCD 201 (FIG. 1). The documentmay be the one which is produced by a word processing software (e.g., MSWord). Footer Preselected Data Storage Area 206A550 b 2 stores the datadescribed hereinafter. User Selected Data Storage Area 206A550 b 3stores the data described hereinafter. Work Area 206A550 b 4 is utilizedas a work area to perform calculation and temporarily store data.

This paragraph illustrates the storage area(s) included in FooterPreselected Data Storage Area 206A550 b 2. In this embodiment, FooterPreselected Data Storage Area 206A550 b 2 includes Footer PreselectedText Data Storage Area 206A550 b 2 a, Footer Preselected Font Type DataStorage Area 206A550 b 2 b, Footer Preselected Font Size Data StorageArea 206A550 b 2 c, Footer Preselected Font Color Data Storage Area206A550 b 2 d, and Footer Preselected Location Data Storage Area 206A550b 2 e. Footer Preselected Text Data Storage Area 206A550 b 2 a storesthe data described hereinafter. Footer Preselected Font Type DataStorage Area 206A550 b 2 b stores the data described hereinafter. FooterPreselected Font Size Data Storage Area 206A550 b 2 c stores the datadescribed hereinafter. Footer Preselected Font Color Data Storage Area206A550 b 2 d stores the data described hereinafter. Footer PreselectedLocation Data Storage Area 206A550 b 2 e stores the data describedhereinafter.

This paragraph illustrates the data stored in Footer Preselected TextData Storage Area 206A550 b 2 a. In this embodiment, Footer PreselectedText Data Storage Area 206A550 b 2 a comprises two columns, i.e.,‘Footer Preselected Text ID’ and ‘Footer Preselected Text Data’. Column‘Footer Preselected Text ID’ stores the footer preselected text IDs, andeach footer preselected text ID is an identification of thecorresponding footer preselected text data stored in column ‘FooterPreselected Text Data’. Each footer preselected text ID may indicate thename or title of the corresponding footer preselected text data. Column‘Footer Preselected Text Data’ stores the footer preselected text data,and each footer preselected text data is the text data capable to beutilized as footer of a document. In this embodiment, Footer PreselectedText Data Storage Area 206A550 b 2 a stores the following data: FooterPreselected Text#1’ and the corresponding ‘Footer Preselected TextData#1’; Footer Preselected Text#2’ and the corresponding ‘FooterPreselected Text Data#2’; Footer Preselected Text#3’ and thecorresponding ‘Footer Preselected Text Data#3’; and Footer PreselectedText#4’ and the corresponding ‘Footer Preselected Text Data#4’.

This paragraph illustrates the data stored in Footer Preselected FontType Data Storage Area 206A550 b 2 b. In this embodiment, FooterPreselected Font Type Data Storage Area 206A550 b 2 b comprises twocolumns, i.e., ‘Footer Preselected Font Type ID’ and ‘Footer PreselectedFont Type Data’. Column ‘Footer Preselected Font Type ID’ stores thefooter preselected font type IDs, and each footer preselected font typeID is an identification of the corresponding footer preselected fonttype data stored in column ‘Footer Preselected Font Type Data’. Eachfooter preselected font type ID may indicate the name or title of thecorresponding footer preselected font type data. Column ‘FooterPreselected Font Type Data’ stores the footer preselected font typedata, and each footer preselected font type data indicates a specificfont type, such as Arial, Times New Roman, Tahoma, or Gothic. In thisembodiment, Footer Preselected Font Type Data Storage Area 206A550 b 2 bstores the following data: Footer Preselected Font Type#1’ and thecorresponding ‘Footer Preselected Font Type Data#1’; Footer PreselectedFont Type#2’ and the corresponding ‘Footer Preselected Font Type Data#2;Footer Preselected Font Type#3’ and the corresponding ‘FooterPreselected Font Type Data#3’; and Footer Preselected Font Type#4’ andthe corresponding ‘Footer Preselected Font Type Data#4’.

This paragraph illustrates the data stored in Footer Preselected FontSize Data Storage Area 206A550 b 2 c. In this embodiment, FooterPreselected Font Size Data Storage Area 206A550 b 2 c comprises twocolumns, i.e., ‘Footer Preselected Font Size ID’ and ‘Footer PreselectedFont Size Data’. Column ‘Footer Preselected Font Size ID’ stores thefooter preselected font size IDs, and each footer preselected font sizeID is an identification of the corresponding footer preselected fontsize data stored in column ‘Footer Preselected Font Size Data’. Eachfooter preselected font size ID may indicate the name or title of thecorresponding footer preselected font size data. Column ‘FooterPreselected Font Size Data’ stores the footer preselected font sizedata, and each footer preselected font size data indicates a specificfont size, such as 8 points, 10 points, 14 points, or 18 points. In thisembodiment, Footer Preselected Font Size Data Storage Area 206A550 b 2 cstores the following data: Footer Preselected Font Size#1’ and thecorresponding ‘Footer Preselected Font Size Data#1’; Footer PreselectedFont Size#2’ and the corresponding ‘Footer Preselected Font Size Data#2;Footer Preselected Font Size#3’ and the corresponding ‘FooterPreselected Font Size Data#3’; and Footer Preselected Font Size#4’ andthe corresponding ‘Footer Preselected Font Size Data#4’.

This paragraph illustrates the data stored in Footer Preselected FontColor Data Storage Area 206A550 b 2 d. In this embodiment, FooterPreselected Font Color Data Storage Area 206A550 b 2 d comprises twocolumns, i.e., ‘Footer Preselected Font Color ID’ and ‘FooterPreselected Font Color Data’. Column ‘Footer Preselected Font Color ID’stores the footer preselected font color IDs, and each footerpreselected font color ID is an identification of the correspondingfooter preselected font color data stored in column ‘Footer PreselectedFont Color Data’. Each footer preselected font color ID may indicate thename or title of the corresponding footer preselected font color data.Column ‘Footer Preselected Font Color Data’ stores the footerpreselected font color data, and each footer preselected font color dataindicates a specific font color, such as red, blue, green or yellow. Inthis embodiment, Footer Preselected Font Color Data Storage Area 206A550b 2 d stores the following data: Footer Preselected Font Color#1’ andthe corresponding ‘Footer Preselected Font Color Data#1’; FooterPreselected Font Color#2’ and the corresponding ‘Footer Preselected FontColor Data#2; Footer Preselected Font Color#3’ and the corresponding‘Footer Preselected Font Color Data#3’; and Footer Preselected FontColor#4’ and the corresponding ‘Footer Preselected Font Color Data#4’.

This paragraph illustrates the data stored in Footer PreselectedLocation Data Storage Area 206A550 b 2 e. In this embodiment, FooterPreselected Location Data Storage Area 206A550 b 2 e comprises twocolumns, i.e., ‘Footer Preselected Location ID’ and ‘Footer PreselectedLocation Data’. Column ‘Footer Preselected Location ID’ stores thefooter preselected location IDs, and each footer preselected location IDis an identification of the corresponding footer preselected locationdata stored in column ‘Footer Preselected Location Data’. Each footerpreselected location ID indicates the name or title of the correspondingfooter preselected location data. Column ‘Footer Preselected LocationData’ stores the footer preselected location data, and each footerpreselected location data indicates the location at which the footer isdisplayed in the document data. In this embodiment, Footer PreselectedLocation Data Storage Area 206A550 b 2 e stores the following data:Footer Preselected Location#1’ and the corresponding ‘Footer PreselectedLocation Data#1’; Footer Preselected Location#2’ and the corresponding‘Footer Preselected Location Data#2; Footer Preselected Location#3’ andthe corresponding ‘Footer Preselected Location Data#3’; and FooterPreselected Location#4’ and the corresponding ‘Footer PreselectedLocation Data#4’.

This paragraph illustrates the storage area(s) included in User SelectedData Storage Area 206A550 b 3. In this embodiment, User Selected DataStorage Area 206A550 b 3 includes Footer Text Data Storage Area 206A550b 3 a, Footer Font Type Data Storage Area 206A550 b 3 b, Footer FontSize Data Storage Area 206A550 b 3 c, Footer Font Color Data StorageArea 206A550 b 3 d, and Footer Location Data Storage Area 206A550 b 3 e.Footer Text Data Storage Area 206A550 b 3 a stores the footer text datawhich is one of the footer preselected text data selected by the user.Footer Font Type Data Storage Area 206A550 b 3 b stores the footer fonttype data which is one of the footer preselected font type data selectedby the user. Footer Font Size Data Storage Area 206A550 b 3 c stores thefooter font size data which is one of the footer preselected font sizedata selected by the user. Footer Font Color Data Storage Area 206A550 b3 d stores the footer font color data which is one of the footerpreselected font color data selected by the user. Footer Location DataStorage Area 206A550 b 3 e stores the footer location data which is oneof the footer preselected location data selected by the user.

This paragraph illustrates the software program(s) stored in FooterDisplaying Software Storage Area 206A550 c. In this embodiment, FooterDisplaying Software Storage Area 206A550 c stores Footer Text DataProducing Software 206A550 c 1, Footer Font Type Data Producing Software206A550 c 2, Footer Font Size Data Producing Software 206A550 c 3,Footer Font Color Data Producing Software 206A550 c 4, Footer LocationData Producing Software 206A550 c 5, Document Footer Displaying Software206A550 c 6, Document Data Transferring Software 206A550 c 7, FooterText Data Transferring Software 206A550 c 8, Footer Font Type DataTransferring Software 206A550 c 9, Footer Font Size Data TransferringSoftware 206A550 c 10, Footer Font Color Data Transferring Software206A550 c 11, Footer Location Data Transferring Software 206A550 c 12,and Document Package Data Transferring Software 206A550 c 13. FooterText Data Producing Software 206A550 c 1 is the software programdescribed hereinafter. Footer Font Type Data Producing Software 206A550c 2 is the software program described hereinafter. Footer Font Size DataProducing Software 206A550 c 3 is the software program describedhereinafter. Footer Font Color Data Producing Software 206A550 c 4 isthe software program described hereinafter. Footer Location DataProducing Software 206A550 c 5 is the software program describedhereinafter. Document Footer Displaying Software 206A550 c 6 is thesoftware program described hereinafter. Document Data TransferringSoftware 206A550 c 7 is the software program described hereinafter.Footer Text Data Transferring Software 206A550 c 8 is the softwareprogram described hereinafter. Footer Font Type Data TransferringSoftware 206A550 c 9 is the software program described hereinafter.Footer Font Size Data Transferring Software 206A550 c 10 is the softwareprogram described hereinafter. Footer Font Color Data TransferringSoftware 206A550 c 11 is the software program described hereinafter.Footer Location Data Transferring Software 206A550 c 12 is the softwareprogram described hereinafter. Document Package Data TransferringSoftware 206A550 c 13 is the software program described hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device B. In this embodiment, RAM 206 includes Footer DisplayingInformation Storage Area 206B550 a of which the data and the softwareprogram(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device B.

This paragraph illustrates the storage area(s) included in FooterDisplaying Information Storage Area 206B550 a. In this embodiment,Footer Displaying Information Storage Area 206B550 a includes FooterDisplaying Data Storage Area 206B550 b and Footer Displaying SoftwareStorage Area 206B550 c. Footer Displaying Data Storage Area 206B550 bstores the data necessary to implement the present function on the sideof Device B, such as the one(s) described hereinafter. Footer DisplayingSoftware Storage Area 206B550 c stores the software program(s) necessaryto implement the present function on the side of Device B, such as theone(s) described hereinafter.

This paragraph illustrates the storage area(s) included in FooterDisplaying Data Storage Area 206B550 b. In this embodiment, FooterDisplaying Data Storage Area 206B550 b includes Document Data StorageArea 206B550 b 1, Footer Preselected Data Storage Area 206B550 b 2, UserSelected Data Storage Area 206B550 b 3, and Work Area 206B550 b 4.Document Data Storage Area 206B550 b 1 stores the document data which isthe document capable to be displayed on LCD 201 (FIG. 1). The documentmay be the one which is produced by a word processing software (e.g., MSWord). Footer Preselected Data Storage Area 206B550 b 2 stores the datadescribed hereinafter. User Selected Data Storage Area 206B550 b 3stores the data described hereinafter. Work Area 206B550 b 4 is utilizedas a work area to perform calculation and temporarily store data.

This paragraph illustrates the storage area(s) included in FooterPreselected Data Storage Area 206B550 b 2. In this embodiment, FooterPreselected Data Storage Area 206B550 b 2 includes Footer PreselectedText Data Storage Area 206B550 b 2 a, Footer Preselected Font Type DataStorage Area 206B550 b 2 b, Footer Preselected Font Size Data StorageArea 206B550 b 2 c, Footer Preselected Font Color Data Storage Area206B550 b 2 d, and Footer Preselected Location Data Storage Area 206B550b 2 e. Footer Preselected Text Data Storage Area 206B550 b 2 a storesthe data described hereinafter. Footer Preselected Font Type DataStorage Area 206B550 b 2 b stores the data described hereinafter. FooterPreselected Font Size Data Storage Area 206B550 b 2 c stores the datadescribed hereinafter. Footer Preselected Font Color Data Storage Area206B550 b 2 d stores the data described hereinafter. Footer PreselectedLocation Data Storage Area 206B550 b 2 e stores the data describedhereinafter.

This paragraph illustrates the data stored in Footer Preselected TextData Storage Area 206B550 b 2 a. In this embodiment, Footer PreselectedText Data Storage Area 206B550 b 2 a comprises two columns, i.e.,‘Footer Preselected Text ID’ and ‘Footer Preselected Text Data’. Column‘Footer Preselected Text ID’ stores the footer preselected text IDs, andeach footer preselected text ID is an identification of thecorresponding footer preselected text data stored in column ‘FooterPreselected Text Data’. Each footer preselected text ID may indicate thename or title of the corresponding footer preselected text data. Column‘Footer Preselected Text Data’ stores the footer preselected text data,and each footer preselected text data is the text data capable to beutilized as footer of a document. In this embodiment, Footer PreselectedText Data Storage Area 206B550 b 2 a stores the following data: FooterPreselected Text#1’ and the corresponding ‘Footer Preselected TextData#1’; Footer Preselected Text#2’ and the corresponding ‘FooterPreselected Text Data#2; Footer Preselected Text#3’ and thecorresponding ‘Footer Preselected Text Data#3’; and Footer PreselectedText#4’ and the corresponding ‘Footer Preselected Text Data#4’.

This paragraph illustrates the data stored in Footer Preselected FontType Data Storage Area 206B550 b 2 b. In this embodiment, FooterPreselected Font Type Data Storage Area 206B550 b 2 b comprises twocolumns, i.e., ‘Footer Preselected Font Type ID’ and ‘Footer PreselectedFont Type Data’. Column ‘Footer Preselected Font Type ID’ stores thefooter preselected font type IDs, and each footer preselected font typeID is an identification of the corresponding footer preselected fonttype data stored in column ‘Footer Preselected Font Type Data’. Eachfooter preselected font type ID may indicate the name or title of thecorresponding footer preselected font type data. Column ‘FooterPreselected Font Type Data’ stores the footer preselected font typedata, and each footer preselected font type data indicates a specificfont type, such as Arial, Times New Roman, Tahoma, or Gothic. In thisembodiment, Footer Preselected Font Type Data Storage Area 206B550 b 2 bstores the following data: Footer Preselected Font Type#1’ and thecorresponding ‘Footer Preselected Font Type Data#1’; Footer PreselectedFont Type#2’ and the corresponding ‘Footer Preselected Font Type Data#2;Footer Preselected Font Type#3’ and the corresponding ‘FooterPreselected Font Type Data#3’; and Footer Preselected Font Type#4’ andthe corresponding ‘Footer Preselected Font Type Data#4’.

This paragraph illustrates the data stored in Footer Preselected FontSize Data Storage Area 206B550 b 2 c. In this embodiment, FooterPreselected Font Size Data Storage Area 206B550 b 2 c comprises twocolumns, i.e., ‘Footer Preselected Font Size ID’ and ‘Footer PreselectedFont Size Data’. Column ‘Footer Preselected Font Size ID’ stores thefooter preselected font size IDs, and each footer preselected font sizeID is an identification of the corresponding footer preselected fontsize data stored in column ‘Footer Preselected Font Size Data’. Eachfooter preselected font size ID may indicate the name or title of thecorresponding footer preselected font size data. Column ‘FooterPreselected Font Size Data’ stores the footer preselected font sizedata, and each footer preselected font size data indicates a specificfont size, such as 8 points, 10 points, 14 points, or 18 points. In thisembodiment, Footer Preselected Font Size Data Storage Area 206B550 b 2 cstores the following data: Footer Preselected Font Size#1’ and thecorresponding ‘Footer Preselected Font Size Data#1’; Footer PreselectedFont Size#2’ and the corresponding ‘Footer Preselected Font Size Data#2;Footer Preselected Font Size#3’ and the corresponding ‘FooterPreselected Font Size Data#3’; and Footer Preselected Font Size#4’ andthe corresponding ‘Footer Preselected Font Size Data#4’.

This paragraph illustrates the data stored in Footer Preselected FontColor Data Storage Area 206B550 b 2 d. In this embodiment, FooterPreselected Font Color Data Storage Area 206B550 b 2 d comprises twocolumns, i.e., ‘Footer Preselected Font Color ID’ and ‘FooterPreselected Font Color Data’. Column ‘Footer Preselected Font Color ID’stores the footer preselected font color IDs, and each footerpreselected font color ID is an identification of the correspondingfooter preselected font color data stored in column ‘Footer PreselectedFont Color Data’. Each footer preselected font color ID may indicate thename or title of the corresponding footer preselected font color data.Column ‘Footer Preselected Font Color Data’ stores the footerpreselected font color data, and each footer preselected font color dataindicates a specific font color, such as red, blue, green or yellow. Inthis embodiment, Footer Preselected Font Color Data Storage Area 206B550b 2 d stores the following data: Footer Preselected Font Color#1’ andthe corresponding ‘Footer Preselected Font Color Data#1’; FooterPreselected Font Color#2’ and the corresponding ‘Footer Preselected FontColor Data#2; Footer Preselected Font Color#3’ and the corresponding‘Footer Preselected Font Color Data#3’; and Footer Preselected FontColor#4’ and the corresponding ‘Footer Preselected Font Color Data#4’.

This paragraph illustrates the data stored in Footer PreselectedLocation Data Storage Area 206B550 b 2 e. In this embodiment, FooterPreselected Location Data Storage Area 206B550 b 2 e comprises twocolumns, i.e., ‘Footer Preselected Location ID’ and ‘Footer PreselectedLocation Data’. Column ‘Footer Preselected Location ID’ stores thefooter preselected location IDs, and each footer preselected location IDis an identification of the corresponding footer preselected locationdata stored in column ‘Footer Preselected Location Data’. Each footerpreselected location ID indicates the name or title of the correspondingfooter preselected location data. Column ‘Footer Preselected LocationData’ stores the footer preselected location data, and each footerpreselected location data indicates the location at which the footer isdisplayed in the document data. In this embodiment, Footer PreselectedLocation Data Storage Area 206B550 b 2 e stores the following data:Footer Preselected Location#1’ and the corresponding ‘Footer PreselectedLocation Data#1’; Footer Preselected Location#2’ and the corresponding‘Footer Preselected Location Data#2; Footer Preselected Location#3’ andthe corresponding ‘Footer Preselected Location Data#3’; and FooterPreselected Location#4’ and the corresponding ‘Footer PreselectedLocation Data#4’.

This paragraph illustrates the storage area(s) included in User SelectedData Storage Area 206B550 b 3. In this embodiment, User Selected DataStorage Area 206B550 b 3 includes Footer Text Data Storage Area 206B550b 3 a, Footer Font Type Data Storage Area 206B550 b 3 b, Footer FontSize Data Storage Area 206B550 b 3 c, Footer Font Color Data StorageArea 206B550 b 3 d, and Footer Location Data Storage Area 206B550 b 3 e.Footer Text Data Storage Area 206B550 b 3 a stores the footer text datawhich is one of the footer preselected text data selected by the user.Footer Font Type Data Storage Area 206B550 b 3 b stores the footer fonttype data which is one of the footer preselected font type data selectedby the user. Footer Font Size Data Storage Area 206B550 b 3 c stores thefooter font size data which is one of the footer preselected font sizedata selected by the user. Footer Font Color Data Storage Area 206B550 b3 d stores the footer font color data which is one of the footerpreselected font color data selected by the user. Footer Location DataStorage Area 206B550 b 3 e stores the footer location data which is oneof the footer preselected location data selected by the user.

This paragraph illustrates the software program(s) stored in FooterDisplaying Software Storage Area 206B550 c. In this embodiment, FooterDisplaying Software Storage Area 206B550 c stores Document FooterDisplaying Software 206B550 c 6, Document Data Transferring Software206B550 c 7, Footer Text Data Transferring Software 206B550 c 8, FooterFont Type Data Transferring Software 206B550 c 9, Footer Font Size DataTransferring Software 206B550 c 10, Footer Font Color Data TransferringSoftware 206B550 c 11, Footer Location Data Transferring Software206B550 c 12, and Document Package Data Transferring Software 206B550 c13. Document Footer Displaying Software 206B550 c 6 is the softwareprogram described hereinafter. Document Data Transferring Software206B550 c 7 is the software program described hereinafter. Footer TextData Transferring Software 206B550 c 8 is the software program describedhereinafter. Footer Font Type Data Transferring Software 206B550 c 9 isthe software program described hereinafter. Footer Font Size DataTransferring Software 206B550 c 10 is the software program describedhereinafter. Footer Font Color Data Transferring Software 206B550 c 11is the software program described hereinafter. Footer Location DataTransferring Software 206B550 c 12 is the software program describedhereinafter. Document Package Data Transferring Software 206B550 c 13 isthe software program described hereinafter.

This paragraph illustrate(s) Footer Text Data Producing Software H550 c1 of Host H and Footer Text Data Producing Software 206A550 c 1 ofDevice A, which produce(s) the footer text data. In this embodiment,Host H retrieves all footer preselected text IDs (e.g., FooterPreselected Text#1 through #4) from Footer Preselected Text Data StorageArea H550 b 2 a and sends the data to Device A (S1). CPU 211 (FIG. 1) ofDevice A receives the footer preselected text IDs (e.g., FooterPreselected Text#1 through #4) from Host H in a wireless fashion anddisplays the data on LCD 201 (FIG. 1) of Device A (S2). The user ofDevice A selects, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, a footer preselected text ID (e.g., FooterPreselected Text#1) (S3). CPU 211 (FIG. 1) of Device A sends the footerpreselected text ID (e.g., Footer Preselected Text#1) selected in theprevious step to Host H in a wireless fashion (S4). Host H receives thefooter preselected text ID (e.g., Footer Preselected Text#1) from DeviceA (S5). Host H retrieves the footer preselected text data (e.g., FooterPreselected Text Data#1) corresponding to the footer preselected text ID(e.g., Footer Preselected Text#1) received in the previous step fromFooter Preselected Text Data Storage Area H550 b 2 a (S6). Host H storesthe footer preselected text data (e.g., Footer Preselected Text Data#1)retrieved in the previous step as the footer text data in Footer TextData Storage Area H550 b 3 a (S7).

This paragraph illustrate(s) Footer Font Type Data Producing SoftwareH550 c 2 of Host H and Footer Font Type Data Producing Software 206A550c 2 of Device A, which produce(s) the footer font type data. In thisembodiment, Host H retrieves all footer preselected font type IDs (e.g.,Footer Preselected Font Type#1 through #4) from Footer Preselected FontType Data Storage Area H550 b 2 b and sends the data to Device A (S1).CPU 211 (FIG. 1) of Device A receives the footer preselected font typeIDs (e.g., Footer Preselected Font Type#1 through #4) from Host H in awireless fashion and displays the data on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a footer preselected font typeID (e.g., Footer Preselected Font Type#1) (S3). CPU 211 (FIG. 1) ofDevice A sends the footer preselected font type ID (e.g., FooterPreselected Font Type#1) selected in the previous step to Host H in awireless fashion (S4). Host H receives the footer preselected font typeID (e.g., Footer Preselected Font Type#1) from Device A (S5). Host Hretrieves the footer preselected font type data (e.g., FooterPreselected Font Type Data#1) corresponding to the footer preselectedfont type ID (e.g., Footer Preselected Font Type#1) received in theprevious step from Footer Preselected Font Type Data Storage Area H550 b2 b (S6). Host H stores the footer preselected font type data (e.g.,Footer Preselected Font Type Data#1) retrieved in the previous step asthe footer font type data in Footer Font Type Data Storage Area H550 b 3b (S7).

This paragraph illustrate(s) Footer Font Size Data Producing SoftwareH550 c 3 of Host H and Footer Font Size Data Producing Software 206A550c 3 of Device A, which produce(s) the footer font size data. In thisembodiment, Host H retrieves all footer preselected font size IDs (e.g.,Footer Preselected Font Size#1 through #4) from Footer Preselected FontSize Data Storage Area H550 b 2 c and sends the data to Device A (S1).CPU 211 (FIG. 1) of Device A receives the footer preselected font sizeIDs (e.g., Footer Preselected Font Size#1 through #4) from Host H in awireless fashion and displays the data on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a footer preselected font sizeID (e.g., Footer Preselected Font Size#1) (S3). CPU 211 (FIG. 1) ofDevice A sends the footer preselected font size ID (e.g., FooterPreselected Font Size#1) selected in the previous step to Host H in awireless fashion (S4). Host H receives the footer preselected font sizeID (e.g., Footer Preselected Font Size#1) from Device A (S5). Host Hretrieves the footer preselected font size data (e.g., FooterPreselected Font Size Data#1) corresponding to the footer preselectedfont size ID (e.g., Footer Preselected Font Size#1) received in theprevious step from Footer Preselected Font Size Data Storage Area H550 b2 c (S6). Host H stores the footer preselected font size data (e.g.,Footer Preselected Font Size Data#1) retrieved in the previous step asthe footer font size data in Footer Font Size Data Storage Area H550 b 3c (S7).

This paragraph illustrate(s) Footer Font Color Data Producing SoftwareH550 c 4 of Host H and Footer Font Color Data Producing Software 206A550c 4 of Device A, which produces) the footer font color data. In thisembodiment, Host H retrieves all footer preselected font color IDs(e.g., Footer Preselected Font Color#1 through #4) from FooterPreselected Font Color Data Storage Area H550 b 2 d and sends the datato Device A (S1). CPU 211 (FIG. 1) of Device A receives the footerpreselected font color IDs (e.g., Footer Preselected Font Color#1through #4) from Host H in a wireless fashion and displays the data onLCD 201 (FIG. 1) of Device A (S2). The user of Device A selects, byutilizing Input Device 210 (FIG. 1) or via voice recognition system, afooter preselected font color ID (e.g., Footer Preselected Font Color#1)(S3). CPU 211 (FIG. 1) of Device A sends the footer preselected fontcolor ID (e.g., Footer Preselected Font Color#1) selected in theprevious step to Host H in a wireless fashion (S4). Host H receives thefooter preselected font color ID (e.g., Footer Preselected Font Color#1)from Device A (S5). Host H retrieves the footer preselected font colordata (e.g., Footer Preselected Font Color Data#1) corresponding to thefooter preselected font color ID (e.g., Footer Preselected Font Color#1)received in the previous step from Footer Preselected Font Color DataStorage Area H550 b 2 d (S6). Host H stores the footer preselected fontcolor data (e.g., Footer Preselected Font Color Data#1) retrieved in theprevious step as the footer font color data in Footer Font Color DataStorage Area H550 b 3 d (S7).

This paragraph illustrate(s) Footer Location Data Producing SoftwareH550 c 5 of Host H and Footer Location Data Producing Software 206A550 c5 of Device A, which produces) the footer location data. In thisembodiment, Host H retrieves all footer preselected location IDs (e.g.,Footer Preselected Location#1 through #4) from Footer PreselectedLocation Data Storage Area H550 b 2 e and sends the data to Device A(S1). CPU 211 (FIG. 1) of Device A receives the footer preselectedlocation IDs (e.g., Footer Preselected Location#1 through #4) from HostH in a wireless fashion and displays the data on LCD 201 (FIG. 1) ofDevice A (S2). The user of Device A selects, by utilizing Input Device210 (FIG. 1) or via voice recognition system, a footer preselectedlocation ID (e.g., Footer Preselected Location#1) (S3). CPU 211 (FIG. 1)of Device A sends the footer preselected location ID (e.g., FooterPreselected Location#1) selected in the previous step to Host H in awireless fashion (S4). Host H receives the footer preselected locationID (e.g., Footer Preselected Location#1) from Device A (S5). Host Hretrieves the footer preselected location data (e.g., Footer PreselectedLocation Data#1) corresponding to the footer preselected location ID(e.g., Footer Preselected Location#1) received in the previous step fromFooter Preselected Location Data Storage Area H550 b 2 e (S6). Host Hstores the footer preselected location data (e.g., Footer PreselectedLocation Data#1) retrieved in the previous step as the footer locationdata in Footer Location Data Storage Area H550 b 3 e (S7).

This paragraph illustrate(s) Document Footer Displaying Software H550 c6 of Host H and Document Footer Displaying Software 206A550 c 6 ofDevice A, which display(s) the footer. In this embodiment, the user ofDevice A inputs, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, the document footer displaying command (S1). Here,the document footer displaying command is the command to display thefooter. CPU 211 (FIG. 1) of Device A sends the document footerdisplaying command input in the previous step to Host H in a wirelessfashion (S2). Host H receives the document footer displaying commandfrom Device A (S3). Host H retrieves the document data from DocumentData Storage Area H550 b 1 and sends the data to Device A (S4). CPU 211(FIG. 1) of Device A receives the document data from Host H in awireless fashion and stores the data in Document Data Storage Area206A550 b 1 (S5). Host H retrieves the footer text data from Footer TextData Storage Area H550 b 3 a and sends the data to Device A (S6). CPU211 (FIG. 1) of Device A receives the footer text data from Host H in awireless fashion and stores the data in Footer Text Data Storage Area206A550 b 3 a (S7). Host H retrieves the footer font type data fromFooter Font Type Data Storage Area H550 b 3 b and sends the data toDevice A (S 8). CPU 211 (FIG. 1) of Device A receives the footer fonttype data from Host H in a wireless fashion and stores the data inFooter Font Type Data Storage Area 206A550 b 3 b (S9). Host H retrievesthe footer font size data from Footer Font Size Data Storage Area H550 b3 c and sends the data to Device A (S10). CPU 211 (FIG. 1) of Device Areceives the footer font size data from Host H in a wireless fashion andstores the data in Footer Font Size Data Storage Area 206A550 b 3 c(S11). Host H retrieves the footer font color data from Footer FontColor Data Storage Area H550 b 3 d and sends the data to Device A (S12).CPU 211 (FIG. 1) of Device A receives the footer font color data fromHost H in a wireless fashion and stores the data in Footer Font ColorData Storage Area 206A550 b 3 d (S13). Host H retrieves the footerlocation data from Footer Location Data Storage Area H550 b 3 e andsends the data to Device A (S14). CPU 211 (FIG. 1) of Device A receivesthe footer location data from Host H in a wireless fashion and storesthe data in Footer Location Data Storage Area 206A550 b 3 e (S15). CPU211 (FIG. 1) of Device A retrieves the document data from Document DataStorage Area 206A550 b 1 (S16). CPU 211 (FIG. 1) of Device A displaysthe document data retrieved in the previous step on LCD 201 (FIG. 1) ofDevice A (S17). CPU 211 (FIG. 1) of Device A retrieves the footer textdata from Footer Text Data Storage Area 206A550 b 3 a (S18). CPU 211(FIG. 1) of Device A retrieves the footer font type data from FooterFont Type Data Storage Area 206A550 b 3 b (S19). CPU 211 (FIG. 1) ofDevice A retrieves the footer font size data from Footer Font Size DataStorage Area 206A550 b 3 c (S20). CPU 211 (FIG. 1) of Device A retrievesthe footer font color data from Footer Font Color Data Storage Area206A550 b 3 d (S21). CPU 211 (FIG. 1) of Device A retrieves the footerlocation data from Footer Location Data Storage Area 206A550 b 3 e(S22). CPU 211 (FIG. 1) of Device A displays the footer text dataretrieved in S18 in accordance with the footer font type data retrievedin S19, Footer Font Size Data retrieved in S20, and the footer fontcolor data retrieved in S21 at the location indicated by the footerlocation data retrieved in S22 on Document Data displayed in S17 (S23).

This paragraph illustrate(s) Document Data Transferring Software H550 c7 of Host H, Document Data Transferring Software 206A550 c 7 of DeviceA, and Document Data Transferring Software 206B550 c 7 of Device B,which transfer(s) the document data. In this embodiment, the user ofDevice A inputs, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, the document data transferring command (S1). Here,the document data transferring command is the command to transfer thedocument data. CPU 211 (FIG. 1) of Device A sends the document datatransferring command input in the previous step to Host H in a wirelessfashion (S2). Host H receives the document data transferring commandfrom Device A (S3). Host H retrieves the document data from DocumentData Storage Area H550 b 1 and sends the data to Device B (S4). CPU 211(FIG. 1) of Device B receives the document data from Host H in awireless fashion and stores the data in Document Data Storage Area206B550 b 1 (S5).

This paragraph illustrate(s) Footer Text Data Transferring Software H550c 8 of Host H, Footer Text Data Transferring Software 206A550 c 8 ofDevice A, and Footer Text Data Transferring Software 206B550 c 8 ofDevice B, which transfer(s) the footer text data. In this embodiment,the user of Device A inputs, by utilizing Input Device 210 (FIG. 1) orvia voice recognition system, the footer text data transferring command(S1). Here, the footer text data transferring command is the command totransfer the footer text data. CPU 211 (FIG. 1) of Device A sends thefooter text data transferring command input in the previous step to HostH in a wireless fashion (S2). Host H receives the footer text datatransferring command from Device A (S3). Host H retrieves the footertext data from Footer Text Data Storage Area H550 b 3 a and sends thedata to Device B (S4). CPU 211 (FIG. 1) of Device B receives the footertext data from Host H in a wireless fashion and stores the data inFooter Text Data Storage Area 206B550 b 3 a (S5).

This paragraph illustrate(s) Footer Font Type Data Transferring SoftwareH550 c 9 of Host H, Footer Font Type Data Transferring Software 206A550c 9 of Device A, and Footer Font Type Data Transferring Software 206B550c 9 of Device B, which transfer(s) the footer font type data. In thisembodiment, the user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the footer font type datatransferring command (S1). Here, the footer font type data transferringcommand is the command to transfer the footer font type data. CPU 211(FIG. 1) of Device A sends the footer font type data transferringcommand input in the previous step to Host H in a wireless fashion (S2).Host H receives the footer font type data transferring command fromDevice A (S3). Host H retrieves the footer font type data from FooterFont Type Data Storage Area H550 b 3 b and sends the data to Device B(S4). CPU 211 (FIG. 1) of Device B receives the footer font type datafrom Host H in a wireless fashion and stores the data in Footer FontType Data Storage Area 206B550 b 3 b (S5).

This paragraph illustrate(s) Footer Font Size Data Transferring SoftwareH550 c 10 of Host H, Footer Font Size Data Transferring Software 206A550c 10 of Device A, and Footer Font Size Data Transferring Software206B550 c 10 of Device B, which transfer(s) the footer font size data.In this embodiment, the user of Device A inputs, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, the footer fontsize data transferring command (S1). Here, the footer font size datatransferring command is the command to transfer the footer font sizedata. CPU 211 (FIG. 1) of Device A sends the footer font size datatransferring command input in the previous step to Host H in a wirelessfashion (S2). Host H receives the footer font size data transferringcommand from Device A (S3). Host H retrieves the footer font size datafrom Footer Font Size Data Storage Area H550 b 3 c and sends the data toDevice B (S4). CPU 211 (FIG. 1) of Device B receives the footer fontsize data from Host H in a wireless fashion and stores the data inFooter Font Size Data Storage Area 206B550 b 3 c (S5).

This paragraph illustrate(s) Footer Font Color Data TransferringSoftware H550 c 11 of Host H, Footer Font Color Data TransferringSoftware 206A550 c 11 of Device A, and Footer Font Color DataTransferring Software 206B550 c 11 of Device B, which transfer(s) thefooter font color data. In this embodiment, the user of Device A inputs,by utilizing Input Device 210 (FIG. 1) or via voice recognition system,the footer font color data transferring command (S1). Here, the footerfont color data transferring command is the command to transfer thefooter font color data. CPU 211 (FIG. 1) of Device A sends the footerfont color data transferring command input in the previous step to HostH in a wireless fashion (S2). Host H receives the footer font color datatransferring command from Device A (S3). Host H retrieves the footerfont color data from Footer Font Color Data Storage Area H550 b 3 d andsends the data to Device B (S4). CPU 211 (FIG. 1) of Device B receivesthe footer font color data from Host H in a wireless fashion and storesthe data in Footer Font Color Data Storage Area 206B550 b 3 d (S5).

This paragraph illustrate(s) Footer Location Data Transferring SoftwareH550 c 12 of Host H, Footer Location Data Transferring Software 206A550c 12 of Device A, and Footer Location Data Transferring Software 206B550c 12 of Device B, which transfer(s) the footer location data. In thisembodiment, the user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the footer location datatransferring command (S1). Here, the footer location data transferringcommand is the command to transfer the footer location data. CPU 211(FIG. 1) of Device A sends the footer location data transferring commandinput in the previous step to Host H in a wireless fashion (S2). Host Hreceives the footer location data transferring command from Device A(S3). Host H retrieves the footer location data from Footer LocationData Storage Area H550 b 3 e and sends the data to Device B (S4). CPU211 (FIG. 1) of Device B receives the footer location data from Host Hin a wireless fashion and stores the data in Footer Location DataStorage Area 206B550 b 3 e (S5).

This paragraph illustrate(s) Document Package Data Transferring SoftwareH550 c 13 of Host H, Document Package Data Transferring Software 206A550c 13 of Device A, and Document Package Data Transferring Software206B550 c 13 of Device B, which transfer(s) the document data and allrelevant data. In this embodiment, the user of Device A inputs, byutilizing Input Device 210 (FIG. 1) or via voice recognition system, thedocument package data transferring command (S1). Here, the documentpackage data transferring command is the command to transfer thedocument data and all relevant data. CPU 211 (FIG. 1) of Device A sendsthe document package data transferring command to Host H in a wirelessfashion (S2). Host H receives the document package data transferringcommand from Device A (S3). Host H retrieves the document data fromDocument Data Storage Area H550 b 1 and sends the data to Device B in awireless fashion (S4). CPU 211 (FIG. 1) of Device B receives thedocument data from Host H in a wireless fashion and stores the data inDocument Data Storage Area 206B550 b 1 (S5). Host H retrieves the footertext data from Footer Text Data Storage Area H550 b 3 a and sends thedata to Device B in a wireless fashion (S6). CPU 211 (FIG. 1) of DeviceB receives the footer text data from Host H in a wireless fashion andstores the data in Footer Text Data Storage Area 206B550 b 3 a (S7).Host H retrieves the footer font type data from Footer Font Type DataStorage Area H550 b 3 b and sends the data to Device B in a wirelessfashion (S8). CPU 211 (FIG. 1) of Device B receives the footer font typedata from Host H in a wireless fashion and stores the data in FooterFont Type Data Storage Area 206B550 b 3 b (S9). Host H retrieves thefooter font size data from Footer Font Size Data Storage Area H550 b 3 cand sends the data to Device B in a wireless fashion (S10). CPU 211(FIG. 1) of Device B receives the footer font size data from Host H in awireless fashion and stores the data in Footer Font Size Data StorageArea 206B550 b 3 c (S11). Host H retrieves the footer font color datafrom Footer Font Color Data Storage Area H550 b 3 d and sends the datato Device B in a wireless fashion (S12). CPU 211 (FIG. 1) of Device Breceives the footer font color data from Host H in a wireless fashionand stores the data in Footer Font Color Data Storage Area 206B550 b 3 d(S13). Host H retrieves the footer location data from Footer LocationData Storage Area H550 b 3 e and sends the data to Device B in awireless fashion (S14). CPU 211 (FIG. 1) of Device B receives the footerlocation data from Host H in a wireless fashion and stores the data inFooter Location Data Storage Area 206B550 b 3 e (S15).

This paragraph illustrate(s) Document Footer Displaying Software 206B550c 6 of Device B, which display(s) the footer. In this embodiment, theuser of Device B inputs, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, the document footer displaying command (S1).Here, the document footer displaying command is the command to displaythe footer. CPU 211 (FIG. 1) of Device B retrieves the document datafrom Document Data Storage Area 206B550 b 1 (S2). CPU 211 (FIG. 1) ofDevice B displays the document data retrieved in the previous step onLCD 201 (FIG. 1) of Device B (S3). CPU 211 (FIG. 1) of Device Bretrieves the footer text data from Footer Text Data Storage Area206B550 b 3 a (S4). CPU 211 (FIG. 1) of Device B retrieves the footerfont type data from Footer Font Type Data Storage Area 206B550 b 3 b(S5). CPU 211 (FIG. 1) of Device B retrieves the footer font size datafrom Footer Font Size Data Storage Area 206B550 b 3 c (S6). CPU 211(FIG. 1) of Device B retrieves the footer font color data from FooterFont Color Data Storage Area 206B550 b 3 d (S7). CPU 211 (FIG. 1) ofDevice B retrieves the footer location data from Footer Location DataStorage Area 206B550 b 3 e (S8). CPU 211 (FIG. 1) of Device B displaysthe footer text data retrieved in S4 in accordance with the footer fonttype data retrieved in S5, Footer Font Size Data retrieved in S6, andthe footer font color data retrieved in S7 at the location indicated bythe footer location data retrieved in S8 on Document Data displayed inS3 (S9).

The following paragraphs illustrate another embodiment wherein Device Aplays the major role in implementing the present function.

This paragraph illustrate(s) Footer Text Data Producing Software 206A550c 1 of Device A, which produce(s) the footer text data. In thisembodiment, CPU 211 (FIG. 1) of Device A retrieves all footerpreselected text IDs (e.g., Footer Preselected Text#1 through #4) fromFooter Preselected Text Data Storage Area 206A550 b 2 a (S1). CPU 211(FIG. 1) of Device A displays the footer preselected text IDs (e.g.,Footer Preselected Text#1 through #4) retrieved in the previous step onLCD 201 (FIG. 1) of Device A (S2). The user of Device A selects, byutilizing Input Device 210 (FIG. 1) or via voice recognition system, afooter preselected text ID (e.g., Footer Preselected Text#1) (S3). CPU211 (FIG. 1) of Device A retrieves the footer preselected text data(e.g., Footer Preselected Text Data#1) corresponding to the footerpreselected text ID (e.g., Footer Preselected Text#1) selected in theprevious step from Footer Preselected Text Data Storage Area 206A550 b 2a (S4). CPU 211 (FIG. 1) of Device A stores the footer preselected textdata (e.g., Footer Preselected Text Data#1) retrieved in the previousstep as the footer text data in Footer Text Data Storage Area 206A550 b3 a (S5).

This paragraph illustrate(s) Footer Font Type Data Producing Software206A550 c 2 of Device A, which produce(s) the footer font type data. Inthis embodiment, CPU 211 (FIG. 1) of Device A retrieves all footerpreselected font type IDs (e.g., Footer Preselected Font Type#1 through#4) from Footer Preselected Font Type Data Storage Area 206A550 b 2 b(S1). CPU 211 (FIG. 1) of Device A displays the footer preselected fonttype IDs (e.g., Footer Preselected Font Type#1 through #4) retrieved inthe previous step on LCD 201 (FIG. 1) of Device A (S2). The user ofDevice A selects, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, a footer preselected font type ID (e.g., FooterPreselected Font Type#1) (S3). CPU 211 (FIG. 1) of Device A retrievesthe footer preselected font type data (e.g., Footer Preselected FontType Data#1) corresponding to the footer preselected font type ID (e.g.,Footer Preselected Font Type#1) selected in the previous step fromFooter Preselected Font Type Data Storage Area 206A550 b 2 b (S4). CPU211 (FIG. 1) of Device A stores the footer preselected font type data(e.g., Footer Preselected Font Type Data#1) retrieved in the previousstep as the footer font type data in Footer Font Type Data Storage Area206A550 b 3 b (S5).

This paragraph illustrate(s) Footer Font Size Data Producing Software206A550 c 3 of Device A, which produce(s) the footer font size data. Inthis embodiment, CPU 211 (FIG. 1) of Device A retrieves all footerpreselected font size IDs (e.g., Footer Preselected Font Size#1 through#4) from Footer Preselected Font Size Data Storage Area 206A550 b 2 c(S1). CPU 211 (FIG. 1) of Device A displays the footer preselected fontsize IDs (e.g., Footer Preselected Font Size#1 through #4) retrieved inthe previous step on LCD 201 (FIG. 1) of Device A (S2). The user ofDevice A selects, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, a footer preselected font size ID (e.g., FooterPreselected Font Size#1) (S3). CPU 211 (FIG. 1) of Device A retrievesthe footer preselected font size data (e.g., Footer Preselected FontSize Data#1) corresponding to the footer preselected font size ID (e.g.,Footer Preselected Font Size#1) selected in the previous step fromFooter Preselected Font Size Data Storage Area 206A550 b 2 c (S4). CPU211 (FIG. 1) of Device A stores the footer preselected font size data(e.g., Footer Preselected Font Size Data#1) retrieved in the previousstep as the footer font size data in Footer Font Size Data Storage Area206A550 b 3 c (S5).

This paragraph illustrate(s) Footer Font Color Data Producing Software206A550 c 4 of Device A, which produce(s) the footer font color data. Inthis embodiment, CPU 211 (FIG. 1) of Device A retrieves all footerpreselected font color IDs (e.g., Footer Preselected Font Color#1through #4) from Footer Preselected Font Color Data Storage Area 206A550b 2 d (S1). CPU 211 (FIG. 1) of Device A displays the footer preselectedfont color IDs (e.g., Footer Preselected Font Color#1 through #4)retrieved in the previous step on LCD 201 (FIG. 1) of Device A (S2). Theuser of Device A selects, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, a footer preselected font color ID (e.g.,Footer Preselected Font Color#1) (S3). CPU 211 (FIG. 1) of Device Aretrieves the footer preselected font color data (e.g., FooterPreselected Font Color Data#1) corresponding to the footer preselectedfont color ID (e.g., Footer Preselected Font Color#1) selected in theprevious step from Footer Preselected Font Color Data Storage Area206A550 b 2 d (S4). CPU 211 (FIG. 1) of Device A stores the footerpreselected font color data (e.g., Footer Preselected Font Color Data#1)retrieved in the previous step as the footer font color data in FooterFont Color Data Storage Area 206A550 b 3 d (S5).

This paragraph illustrate(s) Footer Location Data Producing Software206A550 c 5 of Device A, which produce(s) the footer location data. Inthis embodiment, CPU 211 (FIG. 1) of Device A retrieves all footerpreselected location IDs (e.g., Footer Preselected Location#1 through#4) from Footer Preselected Location Data Storage Area 206A550 b 2 e(S1). CPU 211 (FIG. 1) of Device A displays the footer preselectedlocation IDs (e.g., Footer Preselected Location#1 through #4) retrievedin the previous step on LCD 201 (FIG. 1) of Device A (S2). The user ofDevice A selects, by utilizing Input Device 210 (FIG. 1) or via voicerecognition system, a footer preselected location ID (e.g., FooterPreselected Location#1) (S3). CPU 211 (FIG. 1) of Device A retrieves thefooter preselected location data (e.g., Footer Preselected LocationData#1) corresponding to the footer preselected location ID (e.g.,Footer Preselected Location#1) selected in the previous step from FooterPreselected Location Data Storage Area 206A550 b 2 e (S4). CPU 211(FIG. 1) of Device A stores the footer preselected location data (e.g.,Footer Preselected Location Data#1) retrieved in the previous step asthe footer location data in Footer Location Data Storage Area 206A550 b3 e (S5).

This paragraph illustrate(s) Document Footer Displaying Software 206A550c 6 of Device A, which display(s) the footer. In this embodiment, theuser of Device A inputs, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, the document footer displaying command (S1).Here, the document footer displaying command is the command to displaythe footer. CPU 211 (FIG. 1) of Device A retrieves the document datafrom Document Data Storage Area 206A550 b 1 (S2). CPU 211 (FIG. 1) ofDevice A displays the document data retrieved in the previous step onLCD 201 (FIG. 1) of Device A (S3). CPU 211 (FIG. 1) of Device Aretrieves the footer text data from Footer Text Data Storage Area206A550 b 3 a (S4). CPU 211 (FIG. 1) of Device A retrieves the footerfont type data from Footer Font Type Data Storage Area 206A550 b 3 b(S5). CPU 211 (FIG. 1) of Device A retrieves the footer font size datafrom Footer Font Size Data Storage Area 206A550 b 3 c (S6). CPU 211(FIG. 1) of Device A retrieves the footer font color data from FooterFont Color Data Storage Area 206A550 b 3 d (S7). CPU 211 (FIG. 1) ofDevice A retrieves the footer location data from Footer Location DataStorage Area 206A550 b 3 e (S8). CPU 211 (FIG. 1) of Device A displaysthe footer text data retrieved in S4 in accordance with the footer fonttype data retrieved in S5, Footer Font Size Data retrieved in S6, andthe footer font color data retrieved in S7 at the location indicated bythe footer location data retrieved in S8 on Document Data displayed inS3 (S9).

This paragraph illustrate(s) Document Data Transferring Software 206A550c 7 of Device A and Document Data Transferring Software 206B550 c 7 ofDevice B, which transfer(s) the document data. In this embodiment, theuser of Device A inputs, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, the document data transferring command (S1).Here, the document data transferring command is the command to transferthe document data. CPU 211 (FIG. 1) of Device A retrieves the documentdata from Document Data Storage Area 206A550 b 1 and sends the data toDevice B in a wireless fashion (S2). CPU 211 (FIG. 1) of Device Breceives the document data from Device A in a wireless fashion andstores the data in Document Data Storage Area 206B550 b 1 (S3).

This paragraph illustrate(s) Footer Text Data Transferring Software206A550 c 8 of Device A and Footer Text Data Transferring Software206B550 c 8 of Device B, which transfer(s) the footer text data. In thisembodiment, the user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the footer text datatransferring command (S1). Here, the footer text data transferringcommand is the command to transfer the footer text data. CPU 211(FIG. 1) of Device A retrieves the footer text data from Footer TextData Storage Area 206A550 b 3 a and sends the data to Device B in awireless fashion (S2). CPU 211 (FIG. 1) of Device B receives the footertext data from Device A in a wireless fashion and stores the data inFooter Text Data Storage Area 206B550 b 3 a (S3).

This paragraph illustrate(s) Footer Font Type Data Transferring Software206A550 c 9 of Device A and Footer Font Type Data Transferring Software206B550 c 9 of Device B, which transfer(s) the footer font type data. Inthis embodiment, the user of Device A inputs, by utilizing Input Device210 (FIG. 1) or via voice recognition system, the footer font type datatransferring command (S1). Here, the footer font type data transferringcommand is the command to transfer the footer font type data. CPU 211(FIG. 1) of Device A retrieves the footer font type data from FooterFont Type Data Storage Area 206A550 b 3 b and sends the data to Device Bin a wireless fashion (S2). CPU 211 (FIG. 1) of Device B receives thefooter font type data from Device A in a wireless fashion and stores thedata in Footer Font Type Data Storage Area 206B550 b 3 b (S3).

This paragraph illustrate(s) Footer Font Size Data Transferring Software206A550 c 10 of Device A and Footer Font Size Data Transferring Software206B550 c 10 of Device B, which transfer(s) the footer font size data.In this embodiment, the user of Device A inputs, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, the footer fontsize data transferring command (S1). Here, the footer font size datatransferring command is the command to transfer the footer font sizedata. CPU 211 (FIG. 1) of Device A retrieves the footer font size datafrom Footer Font Size Data Storage Area 206A550 b 3 c and sends the datato Device B in a wireless fashion (S2). CPU 211 (FIG. 1) of Device Breceives the footer font size data from Device A in a wireless fashionand stores the data in Footer Font Size Data Storage Area 206B550 b 3 c(S3).

This paragraph illustrate(s) Footer Font Color Data TransferringSoftware 206A550 c 11 of Device A and Footer Font Color DataTransferring Software 206B550 c 11 of Device B, which transfer(s) thefooter font color data. In this embodiment, the user of Device A inputs,by utilizing Input Device 210 (FIG. 1) or via voice recognition system,the footer font color data transferring command (S1). Here, the footerfont color data transferring command is the command to transfer thefooter font color data. CPU 211 (FIG. 1) of Device A retrieves thefooter font color data from Footer Font Color Data Storage Area 206A550b 3 d and sends the data to Device B in a wireless fashion (S2). CPU 211(FIG. 1) of Device B receives the footer font color data from Device Ain a wireless fashion and stores the data in Footer Font Color DataStorage Area 206B550 b 3 d (S3).

This paragraph illustrate(s) Footer Location Data Transferring Software206A550 c 12 of Device A and Footer Location Data Transferring Software206B550 c 12 of Device B, which transfer(s) the footer location data. Inthis embodiment, the user of Device A inputs, by utilizing Input Device210 (FIG. 1) or via voice recognition system, the footer location datatransferring command (S1). Here, the footer location data transferringcommand is the command to transfer the footer location data. CPU 211(FIG. 1) of Device A retrieves the footer location data from FooterLocation Data Storage Area 206A550 b 3 e and sends the data to Device Bin a wireless fashion (S2). CPU 211 (FIG. 1) of Device B receives thefooter location data from Device A in a wireless fashion and stores thedata in Footer Location Data Storage Area 206B550 b 3 e (S3).

This paragraph illustrate(s) Document Package Data Transferring Software206A550 c 13 of Device A and Document Package Data Transferring Software206B550 c 13 of Device B, which transfer(s) the document data and allrelevant data. In this embodiment, the user of Device A inputs, byutilizing Input Device 210 (FIG. 1) or via voice recognition system, thedocument package data transferring command (S1). Here, the documentpackage data transferring command is the command to transfer thedocument data and all relevant data. CPU 211 (FIG. 1) of Device Aretrieves the document data from Document Data Storage Area 206A550 b 1and sends the data to Device B in a wireless fashion (S2). CPU 211(FIG. 1) of Device B receives the document data from Device A in awireless fashion and stores the data in Document Data Storage Area206B550 b 1 (S3). CPU 211 (FIG. 1) of Device A retrieves the footer textdata from Footer Text Data Storage Area 206A550 b 3 a and sends the datato Device B in a wireless fashion (S4). CPU 211 (FIG. 1) of Device Breceives the footer text data from Device A in a wireless fashion andstores the data in Footer Text Data Storage Area 206B550 b 3 a (S5). CPU211 (FIG. 1) of Device A retrieves the footer font type data from FooterFont Type Data Storage Area 206A550 b 3 b and sends the data to Device Bin a wireless fashion (S6). CPU 211 (FIG. 1) of Device B receives thefooter font type data from Device A in a wireless fashion and stores thedata in Footer Font Type Data Storage Area 206B550 b 3 b (S7). CPU 211(FIG. 1) of Device A retrieves the footer font size data from FooterFont Size Data Storage Area 206A550 b 3 c and sends the data to Device Bin a wireless fashion (S8). CPU 211 (FIG. 1) of Device B receives thefooter font size data from Device A in a wireless fashion and stores thedata in Footer Font Size Data Storage Area 206B550 b 3 c (S9). CPU 211(FIG. 1) of Device A retrieves the footer font color data from FooterFont Color Data Storage Area 206A550 b 3 d and sends the data to DeviceB in a wireless fashion (S10). CPU 211 (FIG. 1) of Device B receives thefooter font color data from Device A in a wireless fashion and storesthe data in Footer Font Color Data Storage Area 206B550 b 3 d (S11). CPU211 (FIG. 1) of Device A retrieves the footer location data from FooterLocation Data Storage Area 206A550 b 3 e and sends the data to Device Bin a wireless fashion (S12). CPU 211 (FIG. 1) of Device B receives thefooter location data from Device A in a wireless fashion and stores thedata in Footer Location Data Storage Area 206B550 b 3 e (S13).

This paragraph illustrate(s) Document Footer Displaying Software 206B550c 6 of Device B, which display(s) the footer. In this embodiment, theuser of Device B inputs, by utilizing Input Device 210 (FIG. 1) or viavoice recognition system, the document footer displaying command (S1).Here, the document footer displaying command is the command to displaythe footer. CPU 211 (FIG. 1) of Device B retrieves the document datafrom Document Data Storage Area 206B550 b 1 (S2). CPU 211 (FIG. 1) ofDevice B displays the document data retrieved in the previous step onLCD 201 (FIG. 1) of Device B (S3). CPU 211 (FIG. 1) of Device Bretrieves the footer text data from Footer Text Data Storage Area206B550 b 3 a (S4). CPU 211 (FIG. 1) of Device B retrieves the footerfont type data from Footer Font Type Data Storage Area 206B550 b 3 b(S5). CPU 211 (FIG. 1) of Device B retrieves the footer font size datafrom Footer Font Size Data Storage Area 206B550 b 3 c (S6). CPU 211(FIG. 1) of Device B retrieves the footer font color data from FooterFont Color Data Storage Area 206B550 b 3 d (S7). CPU 211 (FIG. 1) ofDevice B retrieves the footer location data from Footer Location DataStorage Area 206B550 b 3 e (S8). CPU 211 (FIG. 1) of Device B displaysthe footer text data retrieved in S4 in accordance with the footer fonttype data retrieved in S5, Footer Font Size Data retrieved in S6, andthe footer font color data retrieved in S7 at the location indicated bythe footer location data retrieved in S8 on Document Data displayed inS3 (S9).

<<Location Scheduled Notifying Function>>

The following paragraphs illustrate the location scheduled notifyingfunction, wherein the 1st location which indicates the currentgeographic location of Device A is displayed on Device A at the time anddate identified by Device A. Further, the 2nd location which indicatesthe current geographic location of Device B is displayed on Device A atthe time and date identified by Device A. In addition, the 1st locationand the 2nd location are displayed on Device A at the time and dateidentified by Device A. The notification which notifies that the currentgeographic location of Device A is displayed on Device B is output fromDevice A.

This paragraph illustrates the major elements utilized to implement thepresent function. In this embodiment, Host H is connected to Network NT(e.g., the Internet). Device A, a Communication Device 200, is connectedto Network NT (e.g., the Internet) in a wireless fashion. Device B,another Communication Device 200, is connected to Network NT (e.g., theInternet) in a wireless fashion. Host H, Device A, and Device B arecapable to communicate with each other via Network NT (e.g., theInternet) to implement the present function. Device A and Device B arealso capable to communicate with each other directly in a wirelessfashion to implement the present function.

This paragraph illustrates the storage area included in Host H. In thisembodiment, Host H includes Location Scheduled Notifying InformationStorage Area H551 a of which the data and the software program(s) storedtherein are described hereinafter.

This paragraph illustrates the storage area(s) included in LocationScheduled Notifying Information Storage Area H551 a. In this embodiment,Location Scheduled Notifying Information Storage Area H551 a includesLocation Scheduled Notifying Data Storage Area H551 b and LocationScheduled Notifying Software Storage Area H551 c. Location ScheduledNotifying Data Storage Area H551 b stores the data necessary toimplement the present function on the side of Host H, such as the one(s)described hereinafter. Location Scheduled Notifying Software StorageArea H551 c stores the software program(s) necessary to implement thepresent function on the side of Host H, such as the one(s) describedhereinafter.

This paragraph illustrates the storage area(s) included in LocationScheduled Notifying Data Storage Area H551 b. In this embodiment,Location Scheduled Notifying Data Storage Area H551 b includes PartyLocation Data Storage Area H551 b 1, Party Location Notifying Time DataStorage Area H551 b 2, Map Data Storage Area H551 b 3, Party Icon ImageData Storage Area H551 b 4, Party Location Notifying Data Storage AreaH551 b 5, and Work Area H551 b 6. Party Location Data Storage Area H551b 1 stores the data described hereinafter. Party Location Notifying TimeData Storage Area H551 b 2 stores the data described hereinafter. MapData Storage Area H551 b 3 stores the map data which is the image dataindicating a map. Party Icon Image Data Storage Area H551 b 4 stores thedata described hereinafter. Party Location Notifying Data Storage AreaH551 b 5 stores the data described hereinafter. Work Area H551 b 6 isutilized as a work area to perform calculation and temporarily storedata.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area H551 b 1. In this embodiment, Party LocationData Storage Area H551 b 1 includes 1st Location Data Storage Area H551b 1 a and 2nd Location Data Storage Area H551 b 1 b. 1st Location DataStorage Area H551 b 1 a stores the 1st location data which indicates thecurrent geographic location of Device A in (x,y,z) format. 2nd LocationData Storage Area H551 b 1 b stores the 2nd location data whichindicates the current geographic location of Device B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Time Data Storage Area H551 b 2. In this embodiment,Party Location Notifying Time Data Storage Area H551 b 2 includes 1stLocation Notifying Time Data Storage Area H551 b 2 a, 2nd LocationNotifying Time Data Storage Area H551 b 2 b, and Both Location NotifyingTime Data Storage Area H551 b 2 c. 1st Location Notifying Time DataStorage Area H551 b 2 a stores the 1st location notifying time datawhich indicates the time and date at which the current geographiclocation of Device A is notified. 2nd Location Notifying Time DataStorage Area H551 b 2 b stores the 2nd location notifying time datawhich indicates the time and date at which the current geographiclocation of Device B is notified. Both Location Notifying Time DataStorage Area H551 b 2 c stores the both location notifying time datawhich indicates the time and date at which the current geographiclocations of Device A and Device B are notified.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area H551 b 4. In this embodiment, Party Icon ImageData Storage Area H551 b 4 includes 1st Icon Image Data Storage AreaH551 b 4 a and 2nd Icon Image Data Storage Area H551 b 4 b. 1st IconImage Data Storage Area H551 b 4 a stores the 1st icon image data whichis the image data of the icon indicating the current geographic locationof Device A on the map data. 2nd Icon Image Data Storage Area H551 b 4 bstores the 2nd icon image data which is the image data of the iconindicating the current geographic location of Device B on the map data.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area H551 b 5. In this embodiment, PartyLocation Notifying Data Storage Area H551 b 5 includes 1st LocationNotifying Data Storage Area H551 b 5 a, 2nd Location Notifying DataStorage Area H551 b 5 b, and Both Location Notifying Data Storage AreaH551 b 5 c. 1st Location Notifying Data Storage Area H551 b 5 a storesthe 1st location notifying data which is the audiovisual data notifyingthat the current geographic location of Device A is notified. 2ndLocation Notifying Data Storage Area H551 b 5 b stores the 2nd locationnotifying data which is the audiovisual data notifying that the currentgeographic location of Device B is notified. Both Location NotifyingData Storage Area H551 b 5 c stores the both location notifying datawhich is the audiovisual data notifying that the current geographiclocation of Device A and Device B are notified.

This paragraph illustrates the software program(s) stored in LocationScheduled Notifying Software Storage Area H551 c. In this embodiment,Location Scheduled Notifying Software Storage Area H551 c stores 1stLocation Notifying Time Data Producing Software H551 c1, 2nd LocationNotifying Time Data Producing Software H551 c 2, Both Location NotifyingTime Data Producing Software H551 c 3, 1st Location Data ProducingSoftware H551 c 4, 1st Location Data Notifying Software H551 c 6, 2ndLocation Data Notifying Software H551 c 7, and Both Location DataNotifying Software H551 c 8. 1st Location Notifying Time Data ProducingSoftware H551 c 1 is the software program described hereinafter. 2ndLocation Notifying Time Data Producing Software H551 c 2 is the softwareprogram described hereinafter. Both Location Notifying Time DataProducing Software H551 c 3 is the software program describedhereinafter. 1st Location Data Producing Software H551 c 4 is thesoftware program described hereinafter. 1st Location Data NotifyingSoftware H551 c 6 is the software program described hereinafter. 2ndLocation Data Notifying Software H551 c 7 is the software programdescribed hereinafter. Both Location Data Notifying Software H551 c 8 isthe software program described hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device A. In this embodiment, RAM 206 includes Location ScheduledNotifying Information Storage Area 206A551 a of which the data and thesoftware program(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device A.

This paragraph illustrates the storage area(s) included in LocationScheduled Notifying Information Storage Area 206A551 a. In thisembodiment, Location Scheduled Notifying Information Storage Area206A551 a includes Location Scheduled Notifying Data Storage Area206A551 b and Location Scheduled Notifying Software Storage Area 206A551c. Location Scheduled Notifying Data Storage Area 206A551 b stores thedata necessary to implement the present function on the side of DeviceA, such as the one(s) described in hereinafter. Location ScheduledNotifying Software Storage Area 206A551 c stores the software program(s)necessary to implement the present function on the side of Device A,such as the one(s) described hereinafter.

This paragraph illustrates the storage area(s) included in LocationScheduled Notifying Data Storage Area 206A551 b. In this embodiment,Location Scheduled Notifying Data Storage Area 206A551 b includes PartyLocation Data Storage Area 206A551 b 1, Party Location Notifying TimeData Storage Area 206A551 b 2, Map Data Storage Area 206A551 b 3, PartyIcon Image Data Storage Area 206A551 b 4, Party Location Notifying DataStorage Area 206A551 b 5, and Work Area 206A551 b 6. Party Location DataStorage Area 206A551 b 1 stores the data described hereinafter. PartyLocation Notifying Time Data Storage Area 206A551 b 2 stores the datadescribed hereinafter. Map Data Storage Area 206A551 b 3 stores the mapdata which is the image data indicating a map. Party Icon Image DataStorage Area 206A551 b 4 stores the data described hereinafter. PartyLocation Notifying Data Storage Area 206A551 b 5 stores the datadescribed hereinafter. Work Area 206A551 b 6 is utilized as a work areato perform calculation and temporarily store data.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area 206A551 b 1. In this embodiment, PartyLocation Data Storage Area 206A551 b 1 includes 1st Location DataStorage Area 206A551 b 1 a and 2nd Location Data Storage Area 206A551 b1 b. 1st Location Data Storage Area 206A551 b 1 a stores the 1stlocation data which indicates the current geographic location of DeviceA in (x,y,z) format. 2nd Location Data Storage Area 206A551 b 1 b storesthe 2nd location data which indicates the current geographic location ofDevice B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Time Data Storage Area 206A551 b 2. In thisembodiment, Party Location Notifying Time Data Storage Area 206A551 b 2includes 1st Location Notifying Time Data Storage Area 206A551 b 2 a,2nd Location Notifying Time Data Storage Area 206A551 b 2 b, and BothLocation Notifying Time Data Storage Area 206A551 b 2 c. 1st LocationNotifying Time Data Storage Area 206A551 b 2 a stores the 1st locationnotifying time data which indicates the time and date at which thecurrent geographic location of Device A is notified. 2nd LocationNotifying Time Data Storage Area 206A551 b 2 b stores the 2nd locationnotifying time data which indicates the time and date at which thecurrent geographic location of Device B is notified. Both LocationNotifying Time Data Storage Area 206A551 b 2 c stores the both locationnotifying time data which indicates the time and date at which thecurrent geographic locations of Device A and Device B are notified.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area 206A551 b 4. In this embodiment, Party IconImage Data Storage Area 206A551 b 4 includes 1st Icon Image Data StorageArea 206A551 b 4 a and 2nd Icon Image Data Storage Area 206A551 b 4 b.1st Icon Image Data Storage Area 206A551 b 4 a stores the 1st icon imagedata which is the image data of the icon indicating the currentgeographic location of Device A on the map data. 2nd Icon Image DataStorage Area 206A551 b 4 b stores the 2nd icon image data which is theimage data of the icon indicating the current geographic location ofDevice B on the map data.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area 206A551 b 5. In this embodiment,Party Location Notifying Data Storage Area 206A551 b 5 includes 1stLocation Notifying Data Storage Area 206A551 b 5 a, 2nd LocationNotifying Data Storage Area 206A551 b 5 b, and Both Location NotifyingData Storage Area 206A551 b 5 c. 1st Location Notifying Data StorageArea 206A551 b 5 a stores the 1st location notifying data which is theaudiovisual data notifying that the current geographic location ofDevice A is notified. 2nd Location Notifying Data Storage Area 206A551 b5 b stores the 2nd location notifying data which is the audiovisual datanotifying that the current geographic location of Device B is notified.Both Location Notifying Data Storage Area 206A551 b 5 c stores the bothlocation notifying data which is the audiovisual data notifying that thecurrent geographic location of Device A and Device B are notified.

This paragraph illustrates the software program(s) stored in LocationScheduled Notifying Software Storage Area 206A551 c. In this embodiment,Location Scheduled Notifying Software Storage Area 206A5511 c stores 1stLocation Notifying Time Data Producing Software 206A551 c 1, 2ndLocation Notifying Time Data Producing Software 206A551 c 2, BothLocation Notifying Time Data Producing Software 206A551 c 3, 1stLocation Data Producing Software 206A551 c 4, 1st Location DataNotifying Software 206A551 c 6, 2nd Location Data Notifying Software206A551 c 7, and Both Location Data Notifying Software 206A551 c 8. 1stLocation Notifying Time Data Producing Software 206A551 c 1 is thesoftware program described hereinafter. 2nd Location Notifying Time DataProducing Software 206A551 c 2 is the software program describedhereinafter. Both Location Notifying Time Data Producing Software206A551 c 3 is the software program described hereinafter. 1st LocationData Producing Software 206A551 c 4 is the software program describedhereinafter. 1st Location Data Notifying Software 206A551 c 6 is thesoftware program described hereinafter. 2nd Location Data NotifyingSoftware 206A551 c 7 is the software program described hereinafter. BothLocation Data Notifying Software 206A551 c 8 is the software programdescribed hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device B. In this embodiment, RAM 206 includes Location ScheduledNotifying Information Storage Area 206B551 a of which the data and thesoftware program(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device B.

This paragraph illustrates the storage area(s) included in LocationScheduled Notifying Information Storage Area 206B551 a. In thisembodiment, Location Scheduled Notifying Information Storage Area206B551 a includes Location Scheduled Notifying Data Storage Area206B551 b and Location Scheduled Notifying Software Storage Area 206B551c. Location Scheduled Notifying Data Storage Area 206B551 b stores thedata necessary to implement the present function on the side of DeviceB, such as the one(s) described hereinafter. Location ScheduledNotifying Software Storage Area 206B551 c stores the software program(s)necessary to implement the present function on the side of Device B,such as the one(s) described hereinafter.

This paragraph illustrates the storage area(s) included in LocationScheduled Notifying Data Storage Area 206B551 b. In this embodiment,Location Scheduled Notifying Data Storage Area 206B551 b includes PartyLocation Data Storage Area 206B551 b 1, Party Location Notifying TimeData Storage Area 206B551 b 2, Map Data Storage Area 206B551 b 3, PartyIcon Image Data Storage Area 206B551 b 4, Party Location Notifying DataStorage Area 206B551 b 5, and Work Area 206B551 b 6. Party Location DataStorage Area 206B551 b 1 stores the data described hereinafter. PartyLocation Notifying Time Data Storage Area 206B551 b 2 stores the datadescribed hereinafter. Map Data Storage Area 206B551 b 3 stores the mapdata which is the image data indicating a map. Party Icon Image DataStorage Area 206B551 b 4 stores the data described hereinafter. PartyLocation Notifying Data Storage Area 206B551 b 5 stores the datadescribed hereinafter. Work Area 206B551 b 6 is utilized as a work areato perform calculation and temporarily store data.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area 206B551 b 1. In this embodiment, PartyLocation Data Storage Area 206B551 b 1 includes 1st Location DataStorage Area 206B551 b 1 a and 2nd Location Data Storage Area 206B551 b1 b. 1st Location Data Storage Area 206B551 b 1 a stores the 1stlocation data which indicates the current geographic location of DeviceA in (x,y,z) format. 2nd Location Data Storage Area 206B551 b 1 b storesthe 2nd location data which indicates the current geographic location ofDevice B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Time Data Storage Area 206B551 b 2. In thisembodiment, Party Location Notifying Time Data Storage Area 206B551 b 2includes 1st Location Notifying Time Data Storage Area 206B551 b 2 a,2nd Location Notifying Time Data Storage Area 206B551 b 2 b, and BothLocation Notifying Time Data Storage Area 206B551 b 2 c. 1st LocationNotifying Time Data Storage Area 206B551 b 2 a stores the 1st locationnotifying time data which indicates the time and date at which thecurrent geographic location of Device A is notified. 2nd LocationNotifying Time Data Storage Area 206B551 b 2 b stores the 2nd locationnotifying time data which indicates the time and date at which thecurrent geographic location of Device B is notified. Both LocationNotifying Time Data Storage Area 206B551 b 2 c stores the both locationnotifying time data which indicates the time and date at which thecurrent geographic locations of Device A and Device B are notified.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area 206B551 b 4. In this embodiment, Party IconImage Data Storage Area 206B551 b 4 includes 1st Icon Image Data StorageArea 206B551 b 4 a and 2nd Icon Image Data Storage Area 206B551 b 4 b.1st Icon Image Data Storage Area 206B551 b 4 a stores the 1st icon imagedata which is the image data of the icon indicating the currentgeographic location of Device A on the map data. 2nd Icon Image DataStorage Area 206B551 b 4 b stores the 2nd icon image data which is theimage data of the icon indicating the current geographic location ofDevice B on the map data.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area 206B551 b 5. In this embodiment,Party Location Notifying Data Storage Area 206B551 b 5 includes 1stLocation Notifying Data Storage Area 206B551 b 5 a, 2nd LocationNotifying Data Storage Area 206B551 b 5 b, and Both Location NotifyingData Storage Area 206B551 b 5 c. 1st Location Notifying Data StorageArea 206B551 b 5 a stores the 1st location notifying data which is theaudiovisual data notifying that the current geographic location ofDevice A is notified. 2nd Location Notifying Data Storage Area 206B551 b5 b stores the 2nd location notifying data which is the audiovisual datanotifying that the current geographic location of Device B is notified.Both Location Notifying Data Storage Area 206B551 b 5 c stores the bothlocation notifying data which is the audiovisual data notifying that thecurrent geographic location of Device A and Device B are notified.

This paragraph illustrates the software program(s) stored in LocationScheduled Notifying Software Storage Area 206B551 c. In this embodiment,Location Scheduled Notifying Software Storage Area 206B551 c stores 1stLocation Notifying Time Data Producing Software 206B551 c 1, 2ndLocation Notifying Time Data Producing Software 206B551 c 2, BothLocation Notifying Time Data Producing Software 206B551 c 3, 2ndLocation Data Producing Software 206B551 c 5, 1st Location DataNotifying Software 206B551 c 6, 2nd Location Data Notifying Software206B551 c 7, and Both Location Data Notifying Software 206B551 c 8. 1stLocation Notifying Time Data Producing Software 206B551 c 1 is thesoftware program described hereinafter. 2nd Location Notifying Time DataProducing Software 206B551 c 2 is the software program describedhereinafter. Both Location Notifying Time Data Producing Software206B551 c 3 is the software program described hereinafter. 2nd LocationData Producing Software 206B551 c 5 is the software program describedhereinafter. 1st Location Data Notifying Software 206B551 c 6 is thesoftware program described hereinafter. 2nd Location Data NotifyingSoftware 206B551 c 7 is the software program described hereinafter. BothLocation Data Notifying Software 206B551 c 8 is the software programdescribed hereinafter.

This paragraph illustrate(s) 1st Location Notifying Time Data ProducingSoftware H551 c 1 of Host H and 1st Location Notifying Time DataProducing Software 206A551 c 1 of Device A, which produce(s) the 1stlocation notifying time data. In this embodiment, CPU 211 (FIG. 1) ofDevice A displays the 1st location notifying time data entering area onLCD 201 (FIG. 1) of Device A (S1). Here, the 1st location notifying timedata entering area is the area to input the 1st location notifying timedata. The user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the 1st location notifyingtime data in the 1st location notifying time data entering areadisplayed in the previous step (S2). CPU 211 (FIG. 1) of Device A sendsthe 1st location notifying time data input in the previous step to HostH in a wireless fashion (S3). Host H receives the 1st location notifyingtime data from Device A and stores the data in 1st Location NotifyingTime Data Storage Area H551 b 2 a (S4).

This paragraph illustrate(s) 1st Location Notifying Time Data ProducingSoftware 206B551 c ₁ of Device B, which produce(s) the 1st locationnotifying time data. In this embodiment, CPU 211 (FIG. 1) of Device Bdisplays the 1st location notifying time data entering area on LCD 201(FIG. 1) of Device B (S1). Here, the 1st location notifying time dataentering area is the area to input the 1st location notifying time data.The user of Device B inputs, by utilizing Input Device 210 (FIG. 1) orvia voice recognition system, the 1st location notifying time data inthe 1st location notifying time data entering area displayed in theprevious step (S2). CPU 211 (FIG. 1) of Device B stores the 1st locationnotifying time data input in the previous step in 1st Location NotifyingTime Data Storage Area 206B551 b 2 a (S3).

This paragraph illustrate(s) 2nd Location Notifying Time Data ProducingSoftware H551 c 2 of Host H and 2nd Location Notifying Time DataProducing Software 206A551 c 2 of Device A, which produce(s) the 2ndlocation notifying time data. In this embodiment, CPU 211 (FIG. 1) ofDevice A displays the 2nd location notifying time data entering area onLCD 201 (FIG. 1) of Device A (S1). Here, the 2nd location notifying timedata entering area is the area to input the 2nd location notifying timedata. The user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the 2nd location notifyingtime data in the 2nd location notifying time data entering areadisplayed in the previous step (S2). CPU 211 (FIG. 1) of Device A sendsthe 2nd location notifying time data input in the previous step to HostH in a wireless fashion (S3). Host H receives the 2nd location notifyingtime data from Device A and stores the data in 2nd Location NotifyingTime Data Storage Area H551 b 2 b (S4).

This paragraph illustrate(s) 2nd Location Notifying Time Data ProducingSoftware 206B551 c 2 of Device B, which produce(s) the 2nd locationnotifying time data. In this embodiment, CPU 211 (FIG. 1) of Device Bdisplays the 2nd location notifying time data entering area on LCD 201(FIG. 1) of Device B (S1). Here, the 2nd location notifying time dataentering area is the area to input the 2nd location notifying time data.The user of Device B inputs, by utilizing Input Device 210 (FIG. 1) orvia voice recognition system, the 2nd location notifying time data inthe 2nd location notifying time data entering area displayed in theprevious step (S2). CPU 211 (FIG. 1) of Device B stores the 2nd locationnotifying time data input in the previous step in 2nd Location NotifyingTime Data Storage Area 206B551 b 2 b (S3).

This paragraph illustrate(s) Both Location Notifying Time Data ProducingSoftware H551 c 3 of Host H and Both Location Notifying Time DataProducing Software 206A551 c 3 of Device A, which produce(s) the bothlocation notifying time data. In this embodiment, CPU 211 (FIG. 1) ofDevice A displays the both location notifying time data entering area onLCD 201 (FIG. 1) of Device A (S1). Here, the both location notifyingtime data entering area is the area to input the both location notifyingtime data. The user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the both location notifyingtime data in the both location notifying time data entering areadisplayed in the previous step (S2). CPU 211 (FIG. 1) of Device A sendsthe both location notifying time data input in the previous step to HostH in a wireless fashion (S3). Host H receives the both locationnotifying time data from Device A and stores the data in Both LocationNotifying Time Data Storage Area H551 b 2 c (S4).

This paragraph illustrate(s) Both Location Notifying Time Data ProducingSoftware 206B551 c 3 of Device B, which produce(s) the both locationnotifying time data. In this embodiment, CPU 211 (FIG. 1) of Device Bdisplays the both location notifying time data entering area on LCD 201(FIG. 1) of Device B (S1). Here, the both location notifying time dataentering area is the area to input the both location notifying timedata. The user of Device B inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the both location notifyingtime data in the both location notifying time data entering areadisplayed in the previous step (S2). CPU 211 (FIG. 1) of Device B storesthe both location notifying time data input in the previous step in BothLocation Notifying Time Data Storage Area 206B551 b 2 c (S3).

This paragraph illustrate(s) 1st Location Data Producing Software H551 c4 of Host H and 1st Location Data Producing Software 206A551 c 4 ofDevice A, which produce(s) the 1st location data. In this embodiment,CPU 211 (FIG. 1) of Device A identifies the current location of Device A(S1). CPU 211 (FIG. 1) of Device A produces the 1st location data byutilizing the current location identified in the previous step (S2). CPU211 (FIG. 1) of Device A sends the 1st location data produced in theprevious step to Host H in a wireless fashion (S3). Host H receives the1st location data from Device A and stores the data in 1st Location DataStorage Area H551 b 1 a (S4). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Location Data Producing Software206B551 c 5 of Device B, which produce(s) the 2nd location data. In thisembodiment, CPU 211 (FIG. 1) of Device B identifies the current locationof Device B (S1). CPU 211 (FIG. 1) of Device B produces the 2nd locationdata by utilizing the current location identified in the previous step(S2). CPU 211 (FIG. 1) of Device B stores the 2nd location data producedin the previous step in 2nd Location Data Storage Area 206B551 b 1 b(S3). The foregoing sequence is repeated periodically.

This paragraph illustrate(s) 1st Location Data Notifying Software H551 c6 of Host H and 1st Location Data Notifying Software 206A551 c 6 ofDevice A, which notify(s) the 1st location data. In this embodiment,Host H identifies the current time (S1). Host H retrieves the 1stlocation notifying time data from 1st Location Notifying Time DataStorage Area H551 b 2 a (S2). If the current time identified in S1matches with the 1st location notifying time data retrieved in theprevious step, Host H proceeds to the next step (S3). Host H retrievesthe map data from Map Data Storage Area H551 b 3 and sends the data toDevice A (S4). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S5). Host H retrieves the 1st location data from 1stLocation Data Storage Area H551 b 1 a and sends the data to Device A(S6). CPU 211 (FIG. 1) of Device A receives the 1st location data fromHost H in a wireless fashion (S7). Host H retrieves the 1st icon imagedata from 1st Icon Image Data Storage Area H551 b 4 a and sends the datato Device A (S8). CPU 211 (FIG. 1) of Device A receives the 1st iconimage data from Host H in a wireless fashion (S9). CPU 211 (FIG. 1) ofDevice A displays the 1st icon image data received in the previous stepat the location indicated by the 1st location data received in S7 on themap data displayed in S5 (S10). Host H retrieves the 1st locationnotifying data from 1st Location Notifying Data Storage Area H551 b 5 aand sends the data to Device A (S11). CPU 211 (FIG. 1) of Device Areceives the 1st location notifying data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S12).

This paragraph illustrate(s) 1st Location Data Notifying Software H551 c6 of Host H, 1st Location Data Notifying Software 206A551 c 6 of DeviceA, and 1st Location Data Notifying Software 206B551 c 6 of Device B,which notify(s) the 1st location data. In this embodiment, CPU 211(FIG. 1) of Device B identifies the current time (S1). CPU 211 (FIG. 1)of Device B retrieves the 1st location notifying time data from 1stLocation Notifying Time Data Storage Area 206B551 b 2 a (S2). If thecurrent time identified in S1 matches with the 1st location notifyingtime data retrieved in the previous step, CPU 211 (FIG. 1) of Device Bproceeds to the next step (S3). CPU 211 (FIG. 1) of Device B sends the1st location data transferring request to Host H in a wireless fashion(S4). Here, the 1st location data transferring request is the request totransfer the 1st location data. Host H receives the 1st location datatransferring request from Device B (S5). Host H retrieves the 1stlocation data from 1st Location Data Storage Area H551 b 1 a and sendsthe data to Device B (S6). CPU 211 (FIG. 1) of Device B receives the 1stlocation data from Host H in a wireless fashion and stores the data in1st Location Data Storage Area 206B551 b 1 a (S7). CPU 211 (FIG. 1) ofDevice B retrieves the map data from Map Data Storage Area 206B551 b 3(S8). CPU 211 (FIG. 1) of Device B displays the map data retrieved inthe previous step on LCD 201 (FIG. 1) of Device B (S9). CPU 211 (FIG. 1)of Device B retrieves the 1st location data from 1st Location DataStorage Area 206B551 b 1 a (S10). CPU 211 (FIG. 1) of Device B retrievesthe 1st icon image data from 1st Icon Image Data Storage Area 206B551 b4 a (S11). CPU 211 (FIG. 1) of Device B displays the 1st icon image dataretrieved in the previous step at the location indicated by the 1stlocation data retrieved in S10 on the map data displayed in S9 (S12).CPU 211 (FIG. 1) of Device B retrieves the 1st location notifying datafrom 1st Location Notifying Data Storage Area 206B551 b 5 a (S13). CPU211 (FIG. 1) of Device B outputs the 1st location notifying dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device B (S14). CPU 211 (FIG. 1) of Device B sends the 1stlocation notifying notice to Host H in a wireless fashion (S15). Here,the 1st location notifying notice indicates that the current geographiclocation of Device A is displayed on Device B. Host H receives the 1stlocation notifying notice from Device B (S16). Host H retrieves the 1stlocation notifying data from 1st Location Notifying Data Storage AreaH551 b 5 a and sends the data to Device A (S17). CPU 211 (FIG. 1) ofDevice A receives the 1st location notifying data from Host H in awireless fashion and outputs the data from Speaker 216 (FIG. 1) and LCD201 (FIG. 1) of Device A (S18).

This paragraph illustrate(s) 2nd Location Data Notifying Software H551 c7 of Host H, 2nd Location Data Notifying Software 206A551 c 7 of DeviceA, and 2nd Location Data Notifying Software 206B551 c 7 of Device B,which notify(s) the 2nd location data. In this embodiment, Host Hidentifies the current time (S1). Host H retrieves the 2nd locationnotifying time data from 2nd Location Notifying Time Data Storage AreaH551 b 2 b (S2). If the current time identified in S1 matches with the2nd location notifying time data retrieved in the previous step, Host Hproceeds to the next step (S3). Host H sends the 2nd location datatransferring request to Device B (S4). Here, the 2nd location datatransferring request is the request to transfer the 2nd location data.CPU 211 (FIG. 1) of Device B receives the 2nd location data transferringrequest from Host H in a wireless fashion (S5). CPU 211 (FIG. 1) ofDevice B retrieves the 2nd location data from 2nd Location Data StorageArea 206B551 b 1 b and sends the data to Host H in a wireless fashion(S6). Host H receives the 2nd location data from Device B and stores thedata in 2nd Location Data Storage Area H551 b 1 b (S7). Host H retrievesthe map data from Map Data Storage Area H551 b 3 and sends the data toDevice A (S8). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S9). Host H retrieves the 2nd location data from 2ndLocation Data Storage Area H551 b 1 b and sends the data to Device A(S10). CPU 211 (FIG. 1) of Device A receives the 2nd location data fromHost H in a wireless fashion (S11). Host H retrieves the 2nd icon imagedata from 2nd Icon Image Data Storage Area H551 b 4 b and sends the datato Device A (S12). CPU 211 (FIG. 1) of Device A receives the 2nd iconimage data from Host H in a wireless fashion (S13). CPU 211 (FIG. 1) ofDevice A displays the 2nd icon image data received in the previous stepat the location indicated by the 2nd location data received in S11 onthe map data displayed in S9 (S14). Host H retrieves the 2nd locationnotifying data from 2nd Location Notifying Data Storage Area H551 b 5 band sends the data to Device A (S15). CPU 211 (FIG. 1) of Device Areceives the 2nd location notifying data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S16). Host H sends the 2nd location notifyingnotice to Device B (S17). Here, the 2nd location notifying noticeindicates that the current geographic location of Device B is displayedon Device A. CPU 211 (FIG. 1) of Device B receives the 2nd locationnotifying notice from Host H in a wireless fashion (S18). CPU 211(FIG. 1) of Device B retrieves the 2nd location notifying data from 2ndLocation Notifying Data Storage Area 206B551 b 5 b (S19). CPU 211(FIG. 1) of Device B outputs the 2nd location notifying data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice B (S20).

This paragraph illustrate(s) 2nd Location Data Notifying Software206B551 c 7 of Device B, which notify(s) the 2nd location data. In thisembodiment, CPU 211 (FIG. 1) of Device B identifies the current time(S1). CPU 211 (FIG. 1) of Device B retrieves the 2nd location notifyingtime data from 2nd Location Notifying Time Data Storage Area 206B551 b 2b (S2). If the current time identified in S1 matches with the 2ndlocation notifying time data retrieved in the previous step, CPU 211(FIG. 1) of Device B proceeds to the next step (S3). CPU 211 (FIG. 1) ofDevice B retrieves the map data from Map Data Storage Area 206B551 b 3(S4). CPU 211 (FIG. 1) of Device B displays the map data retrieved inthe previous step on LCD 201 (FIG. 1) of Device B (S5). CPU 211 (FIG. 1)of Device B retrieves the 2nd location data from 2nd Location DataStorage Area 206B551 b 1 b (S6). CPU 211 (FIG. 1) of Device B retrievesthe 2nd icon image data from 2nd Icon Image Data Storage Area 206B551 b4 b (S7). CPU 211 (FIG. 1) of Device B displays the 2nd icon image dataretrieved in the previous step at the location indicated by the 2ndlocation data retrieved in S6 on the map data displayed in S5 (S8). CPU211 (FIG. 1) of Device B retrieves the 2nd location notifying data from2nd Location Notifying Data Storage Area 206B551 b 5 b (S9). CPU 211(FIG. 1) of Device B outputs the 2nd location notifying data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice B (S10).

This paragraph illustrate(s) Both Location Data Notifying Software H551c 8 of Host H, Both Location Data Notifying Software 206A551 c 8 ofDevice A, and Both Location Data Notifying Software 206B551 c 8 ofDevice B, which notify(s) the both location data. In this embodiment,Host H identifies the current time (S1). Host H retrieves the bothlocation notifying time data from Both Location Notifying Time DataStorage Area H551 b 2 c (S2). If the current time identified in S1matches with the both location notifying time data retrieved in theprevious step, Host H proceeds to the next step (S3). Host H sends the2nd location data transferring request to Device B (S4). Here, the 2ndlocation data transferring request is the request to transfer the 2ndlocation data. CPU 211 (FIG. 1) of Device B receives the 2nd locationdata transferring request from Host H in a wireless fashion (S5). CPU211 (FIG. 1) of Device B retrieves the 2nd location data from 2ndLocation Data Storage Area 206B551 b 1 b and sends the data to Host H ina wireless fashion (S6). Host H receives the 2nd location data fromDevice B and stores the data in 2nd Location Data Storage Area H551 b 1b (S7). Host H retrieves the map data from Map Data Storage Area H551 b3 and sends the data to Device A (S8). CPU 211 (FIG. 1) of Device Areceives the map data from Host H in a wireless fashion and displays thedata on LCD 201 (FIG. 1) of Device A (S9). Host H retrieves the 1stlocation data from 1st Location Data Storage Area H551 b 1 a and sendsthe data to Device A (S10). CPU 211 (FIG. 1) of Device A receives the1st location data from Host H in a wireless fashion (S11). Host Hretrieves the 1st icon image data from 1st Icon Image Data Storage AreaH551 b 4 a and sends the data to Device A (S12). CPU 211 (FIG. 1) ofDevice A receives the 1st icon image data from Host H in a wirelessfashion (S13). CPU 211 (FIG. 1) of Device A displays the 1st icon imagedata received in the previous step at the location indicated by the 1stlocation data received in S11 on the map data displayed in S9 (S14).Host H retrieves the 2nd location data from 2nd Location Data StorageArea H551 b 1 b and sends the data to Device A (S15). CPU 211 (FIG. 1)of Device A receives the 2nd location data from Host H in a wirelessfashion (S16). Host H retrieves the 2nd icon image data from 2nd IconImage Data Storage Area H551 b 4 b and sends the data to Device A (S17).CPU 211 (FIG. 1) of Device A receives the 2nd icon image data from HostH in a wireless fashion (S18). CPU 211 (FIG. 1) of Device A displays the2nd icon image data received in the previous step at the locationindicated by the 2nd location data received in S16 on the map datadisplayed in S9 (S19). Thus, the 1st icon image data and the 2nd iconimage data are displayed simultaneously on the map data. Host Hretrieves the both location notifying data from Both Location NotifyingData Storage Area H551 b 5 c and sends the data to Device A (S20). CPU211 (FIG. 1) of Device A receives the both location notifying data fromHost H in a wireless fashion and outputs the data from Speaker 216(FIG. 1) and LCD 201 (FIG. 1) of Device A (S21). Host H sends the 2ndlocation notifying notice to Device B (S22). Here, the 2nd locationnotifying notice indicates that the current geographic location ofDevice B is displayed on Device A. CPU 211 (FIG. 1) of Device B receivesthe 2nd location notifying notice from Host H in a wireless fashion(S23). CPU 211 (FIG. 1) of Device B retrieves the 2nd location notifyingdata from 2nd Location Notifying Data Storage Area 206B551 b 5 b (S24).CPU 211 (FIG. 1) of Device B outputs the 2nd location notifying dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device B (S25).

This paragraph illustrate(s) Both Location Data Notifying Software H551c 8 of Host H, Both Location Data Notifying Software 206A551 c 8 ofDevice A, and Both Location Data Notifying Software 206B551 c 8 ofDevice B, which notify(s) the both location data. In this embodiment,CPU 211 (FIG. 1) of Device B identifies the current time (S1). CPU 211(FIG. 1) of Device B retrieves the both location notifying time datafrom Both Location Notifying Time Data Storage Area 206B551 b 2 c (S2).If the current time identified in S1 matches with the both locationnotifying time data retrieved in the previous step, CPU 211 (FIG. 1) ofDevice B proceeds to the next step (S3). CPU 211 (FIG. 1) of Device Bsends the 1st location data transferring request to Host H in a wirelessfashion (S4). Here, the 1st location data transferring request is therequest to transfer the 1st location data. Host H receives the 1stlocation data transferring request from Device B (S5). Host H retrievesthe 1st location data from 1st Location Data Storage Area H551 b 1 a andsends the data to Device B (S6). CPU 211 (FIG. 1) of Device B receivesthe 1st location data from Host H in a wireless fashion and stores thedata in 1st Location Data Storage Area 206B551 b 1 a (S7). CPU 211(FIG. 1) of Device B retrieves the map data from Map Data Storage Area206B551 b 3 (S8). CPU 211 (FIG. 1) of Device B displays the map dataretrieved in the previous step on LCD 201 (FIG. 1) of Device B (S9). CPU211 (FIG. 1) of Device B retrieves the 1st location data from 1stLocation Data Storage Area 206B551 b 1 a (S10). CPU 211 (FIG. 1) ofDevice B retrieves the 1st icon image data from 1st Icon Image DataStorage Area 206B551 b 4 a (S11). CPU 211 (FIG. 1) of Device B displaysthe 1st icon image data retrieved in the previous step at the locationindicated by the 1st location data retrieved in S10 on the map datadisplayed in S9 (S12). CPU 211 (FIG. 1) of Device B retrieves the 2ndlocation data from 2nd Location Data Storage Area 206B551 b 1 b (S13).CPU 211 (FIG. 1) of Device B retrieves the 2nd icon image data from 2ndIcon Image Data Storage Area 206B551 b 4 b (S14). CPU 211 (FIG. 1) ofDevice B displays the 2nd icon image data retrieved in the previous stepat the location indicated by the 2nd location data retrieved in S13 onthe map data displayed in S9 (S15). Thus, the 1st icon image data andthe 2nd icon image data are displayed simultaneously on the map data.CPU 211 (FIG. 1) of Device B retrieves the both location notifying datafrom Both Location Notifying Data Storage Area 206B551 b 5 c (S16). CPU211 (FIG. 1) of Device B outputs the both location notifying dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device B (S17). CPU 211 (FIG. 1) of Device B sends the 1stlocation notifying notice to Host H in a wireless fashion (S18). Here,the 1st location notifying notice indicates that the current geographiclocation of Device A is displayed on Device B. Host H receives the 1stlocation notifying notice from Device B (S19). Host H retrieves the 1stlocation notifying data from 1st Location Notifying Data Storage AreaH551 b 5 a and sends the data to Device A (S20). CPU 211 (FIG. 1) ofDevice A receives the 1st location notifying data from Host H in awireless fashion and outputs the data from Speaker 216 (FIG. 1) and LCD201 (FIG. 1) of Device A (S21).

The following paragraphs illustrate another embodiment wherein Device Aplays the major role in implementing the present function.

This paragraph illustrate(s) 1st Location Notifying Time Data ProducingSoftware 206A551 c 1 of Device A, which produce(s) the 1st locationnotifying time data. In this embodiment, CPU 211 (FIG. 1) of Device Adisplays the 1st location notifying time data entering area on LCD 201(FIG. 1) of Device A (S1). Here, the 1st location notifying time dataentering area is the area to input the 1st location notifying time data.The user of Device A inputs, by utilizing Input Device 210 (FIG. 1) orvia voice recognition system, the 1st location notifying time data inthe 1st location notifying time data entering area displayed in theprevious step (S2). CPU 211 (FIG. 1) of Device A stores the 1st locationnotifying time data input in the previous step in 1st Location NotifyingTime Data Storage Area 206A551 b 2 a (S3).

This paragraph illustrate(s) 1st Location Notifying Time Data ProducingSoftware 206B551 c 1 of Device B, which produce(s) the 1st locationnotifying time data. In this embodiment, CPU 211 (FIG. 1) of Device Bdisplays the 1st location notifying time data entering area on LCD 201(FIG. 1) of Device B (S1). Here, the 1st location notifying time dataentering area is the area to input the 1st location notifying time data.The user of Device B inputs, by utilizing Input Device 210 (FIG. 1) orvia voice recognition system, the 1st location notifying time data inthe 1st location notifying time data entering area displayed in theprevious step (S2). CPU 211 (FIG. 1) of Device B stores the 1st locationnotifying time data input in the previous step in 1st Location NotifyingTime Data Storage Area 206B551 b 2 a (S3).

This paragraph illustrate(s) 2nd Location Notifying Time Data ProducingSoftware 206A551 c 2 of Device A, which produces) the 2nd locationnotifying time data. In this embodiment, CPU 211 (FIG. 1) of Device Adisplays the 2nd location notifying time data entering area on LCD 201(FIG. 1) of Device A (S1). Here, the 2nd location notifying time dataentering area is the area to input the 2nd location notifying time data.The user of Device A inputs, by utilizing Input Device 210 (FIG. 1) orvia voice recognition system, the 2nd location notifying time data inthe 2nd location notifying time data entering area displayed in theprevious step (S2). CPU 211 (FIG. 1) of Device A stores the 2nd locationnotifying time data input in the previous step in 2nd Location NotifyingTime Data Storage Area 206A551 b 2 b (S3).

This paragraph illustrate(s) 2nd Location Notifying Time Data ProducingSoftware 206B551 c 2 of Device B, which produce(s) the 2nd locationnotifying time data. In this embodiment, CPU 211 (FIG. 1) of Device Bdisplays the 2nd location notifying time data entering area on LCD 201(FIG. 1) of Device B (S1). Here, the 2nd location notifying time dataentering area is the area to input the 2nd location notifying time data.The user of Device B inputs, by utilizing Input Device 210 (FIG. 1) orvia voice recognition system, the 2nd location notifying time data inthe 2nd location notifying time data entering area displayed in theprevious step (S2). CPU 211 (FIG. 1) of Device B stores the 2nd locationnotifying time data input in the previous step in 2nd Location NotifyingTime Data Storage Area 206B551 b 2 b (S3).

This paragraph illustrate(s) Both Location Notifying Time Data ProducingSoftware 206A551 c 3 of Device A, which produce(s) the both locationnotifying time data. In this embodiment, CPU 211 (FIG. 1) of Device Adisplays the both location notifying time data entering area on LCD 201(FIG. 1) of Device A (S1). Here, the both location notifying time dataentering area is the area to input the both location notifying timedata. The user of Device A inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the both location notifyingtime data in the both location notifying time data entering areadisplayed in the previous step (S2). CPU 211 (FIG. 1) of Device A storesthe both location notifying time data input in the previous step in BothLocation Notifying Time Data Storage Area 206A551 b 2 c (S3).

This paragraph illustrate(s) Both Location Notifying Time Data ProducingSoftware 206B551 c 3 of Device B, which produce(s) the both locationnotifying time data. In this embodiment, CPU 211 (FIG. 1) of Device Bdisplays the both location notifying time data entering area on LCD 201(FIG. 1) of Device B (S1). Here, the both location notifying time dataentering area is the area to input the both location notifying timedata. The user of Device B inputs, by utilizing Input Device 210(FIG. 1) or via voice recognition system, the both location notifyingtime data in the both location notifying time data entering areadisplayed in the previous step (S2). CPU 211 (FIG. 1) of Device B storesthe both location notifying time data input in the previous step in BothLocation Notifying Time Data Storage Area 206B551 b 2 c (S3).

This paragraph illustrate(s) 1st Location Data Producing Software206A551 c 4 of Device A, which produce(s) the 1st location data. In thisembodiment, CPU 211 (FIG. 1) of Device A identifies the current locationof Device A (S1). CPU 211 (FIG. 1) of Device A produces the 1st locationdata by utilizing the current location identified in the previous step(S2). CPU 211 (FIG. 1) of Device A stores the 1st location data producedin the previous step in 1st Location Data Storage Area 206A551 b 1 a(S3). The foregoing sequence is repeated periodically.

This paragraph illustrate(s) 2nd Location Data Producing Software206B551 c 5 of Device B, which produce(s) the 2nd location data. In thisembodiment, CPU 211 (FIG. 1) of Device B identifies the current locationof Device B (S1). CPU 211 (FIG. 1) of Device B produces the 2nd locationdata by utilizing the current location identified in the previous step(S2). CPU 211 (FIG. 1) of Device B stores the 2nd location data producedin the previous step in 2nd Location Data Storage Area 206B551 b 1 b(S3). The foregoing sequence is repeated periodically.

This paragraph illustrate(s) 1st Location Data Notifying Software206A551 c 6 of Device A, which notify(s) the 1st location data. In thisembodiment, CPU 211 (FIG. 1) of Device A identifies the current time(S1). CPU 211 (FIG. 1) of Device A retrieves the 1st location notifyingtime data from 1st Location Notifying Time Data Storage Area 206A551 b 2a (S2). If the current time identified in S1 matches with the 1stlocation notifying time data retrieved in the previous step, CPU 211(FIG. 1) of Device A proceeds to the next step (S3). CPU 211 (FIG. 1) ofDevice A retrieves the map data from Map Data Storage Area 206A551 b 3(S4). CPU 211 (FIG. 1) of Device A displays the map data retrieved inthe previous step on LCD 201 (FIG. 1) of Device A (S5). CPU 211 (FIG. 1)of Device A retrieves the 1st location data from 1st Location DataStorage Area 206A551 b 1 a (S6). CPU 211 (FIG. 1) of Device A retrievesthe 1st icon image data from 1st Icon Image Data Storage Area 206A551 b4 a (S7). CPU 211 (FIG. 1) of Device A displays the 1st icon image dataretrieved in the previous step at the location indicated by the 1stlocation data retrieved in S6 on the map data displayed in S5 (S8). CPU211 (FIG. 1) of Device A retrieves the 1st location notifying data from1st Location Notifying Data Storage Area 206A551 b 5 a (S9). CPU 211(FIG. 1) of Device A outputs the 1st location notifying data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice A (S10).

This paragraph illustrate(s) 1st Location Data Notifying Software206A551 c 6 of Device A and 1st Location Data Notifying Software 206B551c 6 of Device B, which notify(s) the 1st location data. In thisembodiment, CPU 211 (FIG. 1) of Device B identifies the current time(S1). CPU 211 (FIG. 1) of Device B retrieves the 1st location notifyingtime data from 1st Location Notifying Time Data Storage Area 206B551 b 2a (S2). If the current time identified in S1 matches with the 1stlocation notifying time data retrieved in the previous step, CPU 211(FIG. 1) of Device B proceeds to the next step (S3). CPU 211 (FIG. 1) ofDevice B sends the 1st location data transferring request to Device A ina wireless fashion (S4). Here, the 1st location data transferringrequest is the request to transfer the 1st location data. CPU 211(FIG. 1) of Device A receives the 1st location data transferring requestfrom Device B in a wireless fashion (S5). CPU 211 (FIG. 1) of Device Aretrieves the 1st location data from 1st Location Data Storage Area206A551 b 1 a and sends the data to Device B in a wireless fashion (S6).CPU 211 (FIG. 1) of Device B receives the 1st location data from DeviceA in a wireless fashion and stores the data in 1st Location Data StorageArea 206B551 b 1 a (S7). CPU 211 (FIG. 1) of Device B retrieves the mapdata from Map Data Storage Area 206B551 b 3 (S8). CPU 211 (FIG. 1) ofDevice B displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device B (S9). CPU 211 (FIG. 1) of Device B retrieves the1st location data from 1st Location Data Storage Area 206B551 b 1 a(S10). CPU 211 (FIG. 1) of Device B retrieves the 1st icon image datafrom 1st Icon Image Data Storage Area 206B551 b 4 a (S11). CPU 211(FIG. 1) of Device B displays the 1st icon image data retrieved in theprevious step at the location indicated by the 1st location dataretrieved in S10 on the map data displayed in S9 (S12). CPU 211 (FIG. 1)of Device B retrieves the 1st location notifying data from 1st LocationNotifying Data Storage Area 206B551 b 5 a (S13). CPU 211 (FIG. 1) ofDevice B outputs the 1st location notifying data retrieved in theprevious step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B(S14). CPU 211 (FIG. 1) of Device B sends the 1st location notifyingnotice to Device A in a wireless fashion (S15). Here, the 1st locationnotifying notice indicates that the current geographic location ofDevice A is displayed on Device B. CPU 211 (FIG. 1) of Device A receivesthe 1st location notifying notice from Device B in a wireless fashion(S16). CPU 211 (FIG. 1) of Device A retrieves the 1st location notifyingdata from 1st Location Notifying Data Storage Area 206A551 b 5 a (S17).CPU 211 (FIG. 1) of Device A outputs the 1st location notifying dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S18).

This paragraph illustrate(s) 2nd Location Data Notifying Software206A551 c 7 of Device A and 2nd Location Data Notifying Software 206B551c 7 of Device B, which notify(s) the 2nd location data. In thisembodiment, CPU 211 (FIG. 1) of Device A identifies the current time(S1). CPU 211 (FIG. 1) of Device A retrieves the 2nd location notifyingtime data from 2nd Location Notifying Time Data Storage Area 206A551 b 2b (S2). If the current time identified in S1 matches with the 2ndlocation notifying time data retrieved in the previous step, CPU 211(FIG. 1) of Device A proceeds to the next step (S3). CPU 211 (FIG. 1) ofDevice A sends the 2nd location data transferring request to Device B ina wireless fashion (S4). Here, the 2nd location data transferringrequest is the request to transfer the 2nd location data. CPU 211(FIG. 1) of Device B receives the 2nd location data transferring requestfrom Device A in a wireless fashion (S5). CPU 211 (FIG. 1) of Device Bretrieves the 2nd location data from 2nd Location Data Storage Area206B551 b 1 b and sends the data to Device A in a wireless fashion (S6).CPU 211 (FIG. 1) of Device A receives the 2nd location data from DeviceB in a wireless fashion and stores the data in 2nd Location Data StorageArea 206A551 b 1 b (S7). CPU 211 (FIG. 1) of Device A retrieves the mapdata from Map Data Storage Area 206A551 b 3 (S8). CPU 211 (FIG. 1) ofDevice A displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device A (S9). CPU 211 (FIG. 1) of Device A retrieves the2nd location data from 2nd Location Data Storage Area 206A551 b 1 b(S10). CPU 211 (FIG. 1) of Device A retrieves the 2nd icon image datafrom 2nd Icon Image Data Storage Area 206A551 b 4 b (S11). CPU 211(FIG. 1) of Device A displays the 2nd icon image data retrieved in theprevious step at the location indicated by the 2nd location dataretrieved in S10 on the map data displayed in S9 (S12). CPU 211 (FIG. 1)of Device A retrieves the 2nd location notifying data from 2nd LocationNotifying Data Storage Area 206A551 b 5 b (S13). CPU 211 (FIG. 1) ofDevice A outputs the 2nd location notifying data retrieved in theprevious step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device A(S14). CPU 211 (FIG. 1) of Device A sends the 2nd location notifyingnotice to Device B in a wireless fashion (S15). Here, the 2nd locationnotifying notice indicates that the current geographic location ofDevice B is displayed on Device A. CPU 211 (FIG. 1) of Device B receivesthe 2nd location notifying notice from Device A in a wireless fashion(S16). CPU 211 (FIG. 1) of Device B retrieves the 2nd location notifyingdata from 2nd Location Notifying Data Storage Area 206B551 b 5 b (S17).CPU 211 (FIG. 1) of Device B outputs the 2nd location notifying dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device B (S18).

This paragraph illustrate(s) 2nd Location Data Notifying Software206B551 c 7 of Device B, which notify(s) the 2nd location data. In thisembodiment, CPU 211 (FIG. 1) of Device B identifies the current time(S1). CPU 211 (FIG. 1) of Device B retrieves the 2nd location notifyingtime data from 2nd Location Notifying Time Data Storage Area 206B551 b 2b (S2). If the current time identified in S1 matches with the 2ndlocation notifying time data retrieved in the previous step, CPU 211(FIG. 1) of Device B proceeds to the next step (S3). CPU 211 (FIG. 1) ofDevice B retrieves the map data from Map Data Storage Area 206B551 b 3(S4). CPU 211 (FIG. 1) of Device B displays the map data retrieved inthe previous step on LCD 201 (FIG. 1) of Device B (S5). CPU 211 (FIG. 1)of Device B retrieves the 2nd location data from 2nd Location DataStorage Area 206B551 b 1 b (S6). CPU 211 (FIG. 1) of Device B retrievesthe 2nd icon image data from 2nd Icon Image Data Storage Area 206B551 b4 b (S7). CPU 211 (FIG. 1) of Device B displays the 2nd icon image dataretrieved in the previous step at the location indicated by the 2ndlocation data retrieved in S6 on the map data displayed in S5 (S8). CPU211 (FIG. 1) of Device B retrieves the 2nd location notifying data from2nd Location Notifying Data Storage Area 206B551 b 5 b (S9). CPU 211(FIG. 1) of Device B outputs the 2nd location notifying data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice B (S10).

This paragraph illustrate(s) Both Location Data Notifying Software206A551 c 8 of Device A and Both Location Data Notifying Software206B551 c 8 of Device B, which notify(s) the both location data. In thisembodiment, CPU 211 (FIG. 1) of Device A identifies the current time(S1). CPU 211 (FIG. 1) of Device A retrieves the both location notifyingtime data from Both Location Notifying Time Data Storage Area 206A551 b2 c (S2). If the current time identified in S1 matches with the bothlocation notifying time data retrieved in the previous step, CPU 211(FIG. 1) of Device A proceeds to the next step (S3). CPU 211 (FIG. 1) ofDevice A sends the 2nd location data transferring request to Device B ina wireless fashion (S4). Here, the 2nd location data transferringrequest is the request to transfer the 2nd location data. CPU 211(FIG. 1) of Device B receives the 2nd location data transferring requestfrom Device A in a wireless fashion (S5). CPU 211 (FIG. 1) of Device Bretrieves the 2nd location data from 2nd Location Data Storage Area206B551 b 1 b and sends the data to Device A in a wireless fashion (S6).CPU 211 (FIG. 1) of Device A receives the 2nd location data from DeviceB in a wireless fashion and stores the data in 2nd Location Data StorageArea 206A551 b 1 b (S7). CPU 211 (FIG. 1) of Device A retrieves the mapdata from Map Data Storage Area 206A551 b 3 (S8). CPU 211 (FIG. 1) ofDevice A displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device A (S9). CPU 211 (FIG. 1) of Device A retrieves the1st location data from 1st Location Data Storage Area 206A551 b 1 a(S10). CPU 211 (FIG. 1) of Device A retrieves the 1st icon image datafrom 1st Icon Image Data Storage Area 206A551 b 4 a (S11). CPU 211(FIG. 1) of Device A displays the 1st icon image data retrieved in theprevious step at the location indicated by the 1st location dataretrieved in S10 on the map data displayed in S9 (S12). CPU 211 (FIG. 1)of Device A retrieves the 2nd location data from 2nd Location DataStorage Area 206A551 b 1 b (S13). CPU 211 (FIG. 1) of Device A retrievesthe 2nd icon image data from 2nd Icon Image Data Storage Area 206A551 b4 b (S14). CPU 211 (FIG. 1) of Device A displays the 2nd icon image dataretrieved in the previous step at the location indicated by the 2ndlocation data retrieved in S13 on the map data displayed in S9 (S15).Thus, the 1st icon image data and the 2nd icon image data are displayedsimultaneously on the map data. CPU 211 (FIG. 1) of Device A retrievesthe both location notifying data from Both Location Notifying DataStorage Area 206A551 b 5 c (S16). CPU 211 (FIG. 1) of Device A outputsthe both location notifying data retrieved in the previous step fromSpeaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device A (S17). CPU 211(FIG. 1) of Device A sends the 2nd location notifying notice to Device Bin a wireless fashion (S18). Here, the 2nd location notifying noticeindicates that the current geographic location of Device B is displayedon Device A. CPU 211 (FIG. 1) of Device B receives the 2nd locationnotifying notice from Device A in a wireless fashion (S19). CPU 211(FIG. 1) of Device B retrieves the 2nd location notifying data from 2ndLocation Notifying Data Storage Area 206B551 b 5 b (S20). CPU 211(FIG. 1) of Device B outputs the 2nd location notifying data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice B (S21).

This paragraph illustrate(s) Both Location Data Notifying Software206A551 c 8 of Device A and Both Location Data Notifying Software206B551 c 8 of Device B, which notify(s) the both location data. In thisembodiment, CPU 211 (FIG. 1) of Device B identifies the current time(S1). CPU 211 (FIG. 1) of Device B retrieves the both location notifyingtime data from Both Location Notifying Time Data Storage Area 206B551 b2 c (S2). If the current time identified in S1 matches with the bothlocation notifying time data retrieved in the previous step, CPU 211(FIG. 1) of Device B proceeds to the next step (S3). CPU 211 (FIG. 1) ofDevice B sends the 1st location data transferring request to Device A ina wireless fashion (S4). Here, the 1st location data transferringrequest is the request to transfer the 1st location data. CPU 211(FIG. 1) of Device A receives the 1st location data transferring requestfrom Device B in a wireless fashion (S5). CPU 211 (FIG. 1) of Device Aretrieves the 1st location data from 1st Location Data Storage Area206A551 b 1 a and sends the data to Device B in a wireless fashion (S6).CPU 211 (FIG. 1) of Device B receives the 1st location data from DeviceA in a wireless fashion and stores the data in 1st Location Data StorageArea 206B551 b 1 a (S7). CPU 211 (FIG. 1) of Device B retrieves the mapdata from Map Data Storage Area 206B551 b 3 (S8). CPU 211 (FIG. 1) ofDevice B displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device B (S9). CPU 211 (FIG. 1) of Device B retrieves the1st location data from 1st Location Data Storage Area 206B551 b 1 a(S10). CPU 211 (FIG. 1) of Device B retrieves the 1st icon image datafrom 1st Icon Image Data Storage Area 206B551 b 4 a (S11). CPU 211(FIG. 1) of Device B displays the 1st icon image data retrieved in theprevious step at the location indicated by the 1st location dataretrieved in S10 on the map data displayed in S9 (S12). CPU 211 (FIG. 1)of Device B retrieves the 2nd location data from 2nd Location DataStorage Area 206B551 b 1 b (S13). CPU 211 (FIG. 1) of Device B retrievesthe 2nd icon image data from 2nd Icon Image Data Storage Area 206B551 b4 b (S14). CPU 211 (FIG. 1) of Device B displays the 2nd icon image dataretrieved in the previous step at the location indicated by the 2ndlocation data retrieved in S13 on the map data displayed in S9 (S15).Thus, the 1st icon image data and the 2nd icon image data are displayedsimultaneously on the map data. CPU 211 (FIG. 1) of Device B retrievesthe both location notifying data from Both Location Notifying DataStorage Area 206B551 b 5 c (S16). CPU 211 (FIG. 1) of Device B outputsthe both location notifying data retrieved in the previous step fromSpeaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B (S17). CPU 211(FIG. 1) of Device B sends the 1st location notifying notice to Device Ain a wireless fashion (S18). Here, the 1st location notifying noticeindicates that the current geographic location of Device A is displayedon Device B. CPU 211 (FIG. 1) of Device A receives the 1st locationnotifying notice from Device B in a wireless fashion (S19). CPU 211(FIG. 1) of Device A retrieves the 1st location notifying data from 1stLocation Notifying Data Storage Area 206A551 b 5 a (S20). CPU 211(FIG. 1) of Device A outputs the 1st location notifying data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice A (S21).

<<Zone Leaving Notifying Function>>

The following paragraphs illustrate the zone leaving notifying function,wherein when Device A leaves from a specific geographic zone identifiedby Device A, a notice is output from Device A. The notice is furtheroutput from Device B. In addition, when Device B leaves from a specificgeographic zone identified by Device A, a notice is output from DeviceA.

This paragraph illustrates the major elements utilized to implement thepresent function. In this embodiment, Host H is connected to Network NT(e.g., the Internet). Device A, a Communication Device 200, is connectedto Network NT (e.g., the Internet) in a wireless fashion. Device B,another Communication Device 200, is connected to Network NT (e.g., theInternet) in a wireless fashion. Host H, Device A, and Device B arecapable to communicate with each other via Network NT (e.g., theInternet) to implement the present function. Device A and Device B arealso capable to communicate with each other directly in a wirelessfashion to implement the present function.

This paragraph illustrates the storage area included in Host H. In thisembodiment, Host H includes Zone Leaving Notifying Information StorageArea H552 a of which the data and the software program(s) stored thereinare described hereinafter.

This paragraph illustrates the storage area(s) included in Zone LeavingNotifying Information Storage Area H552 a. In this embodiment, ZoneLeaving Notifying Information Storage Area H552 a includes Zone LeavingNotifying Data Storage Area H552 b and Zone Leaving Notifying SoftwareStorage Area H552 c. Zone Leaving Notifying Data Storage Area H552 bstores the data necessary to implement the present function on the sideof Host H, such as the one(s) described hereinafter. Zone LeavingNotifying Software Storage Area H552 c stores the software program(s)necessary to implement the present function on the side of Host H, suchas the one(s) described hereinafter.

This paragraph illustrates the storage area(s) included in Zone LeavingNotifying Data Storage Area H552 b. In this embodiment, Zone LeavingNotifying Data Storage Area H552 b includes Map Data Storage Area H552 b1, Party Zone Data Storage Area H552 b 2, Party Location Data StorageArea H552 b 3, Party Zone Leaving Notice Data Storage Area H552 b 4,Party Icon Image Data Storage Area H552 b 5, Party Location NotifyingData Storage Area H552 b 6, and Work Area H552 b 7. Map Data StorageArea H552 b 1 stores the map data which is the image data indicating amap. Party Zone Data Storage Area H552 b 2 stores the data describedhereinafter. Party Location Data Storage Area H552 b 3 stores the datadescribed hereinafter. Party Zone Leaving Notice Data Storage Area H552b 4 stores the data described hereinafter. Party Icon Image Data StorageArea H552 b 5 stores the data described hereinafter. Party LocationNotifying Data Storage Area H552 b 6 stores the data describedhereinafter. Work Area H552 b 7 is utilized as a work area to performcalculation and temporarily store data.

This paragraph illustrates the storage area(s) included in Party ZoneData Storage Area H552 b 2. In this embodiment, Party Zone Data StorageArea H552 b 2 includes 1st Zone Data Storage Area H552 b 2 a, 2nd ZoneData Storage Area H552 b 2 b, 3rd Zone Data Storage Area H552 b 2 c, and4th Zone Data Storage Area H552 b 2 d. 1st Zone Data Storage Area H552 b2 a stores the 1st zone data which indicates a certain geographic zoneor area. 2nd Zone Data Storage Area H552 b 2 b stores the 2nd zone datawhich indicates a certain geographic zone or area. 3rd Zone Data StorageArea H552 b 2 c stores the 3rd zone data which indicates a certaingeographic zone or area. 4th Zone Data Storage Area H552 b 2 d storesthe 4th zone data which indicates a certain geographic zone or area.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area H552 b 3. In this embodiment, Party LocationData Storage Area H552 b 3 includes Device A Location Data Storage AreaH552 b 3 a and Device B Location Data Storage Area H552 b 3 b. Device ALocation Data Storage Area H552 b 3 a stores the Device A location datawhich indicates the current geographic location of Device A in (x,y,z)format. Device B Location Data Storage Area H552 b 3 b stores the DeviceB location data which indicates the current geographic location ofDevice B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in Party ZoneLeaving Notice Data Storage Area H552 b 4. In this embodiment, PartyZone Leaving Notice Data Storage Area H552 b 4 includes 1st Zone LeavingNotice Data Storage Area H552 b 4 a, 2nd Zone Leaving Notice DataStorage Area H552 b 4 b, 3rd Zone Leaving Notice Data Storage Area H552b 4 c, and 4th Zone Leaving Notice Data Storage Area H552 b 4 d. 1stZone Leaving Notice Data Storage Area H552 b 4 a stores the 1st zoneleaving notice data which is the audiovisual data indicating that DeviceA left the zone indicated by the 1st zone data. 2nd Zone Leaving NoticeData Storage Area H552 b 4 b stores the 2nd zone leaving notice datawhich is the audiovisual data indicating that Device A left the zoneindicated by the 2nd zone data. 3rd Zone Leaving Notice Data StorageArea H552 b 4 c stores the 3rd zone leaving notice data which is theaudiovisual data indicating that Device B left the zone indicated by the3rd zone data. 4th Zone Leaving Notice Data Storage Area H552 b 4 dstores the 4th zone leaving notice data which is the audiovisual dataindicating that Device B left the zone indicated by the 4th zone data.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area H552 b 5. In this embodiment, Party Icon ImageData Storage Area H552 b 5 includes Device A Icon Image Data StorageArea H552 b 5 a and Device B Icon Image Data Storage Area H552 b 5 b.Device A Icon Image Data Storage Area H552 b 5 a stores the Device Aicon image data which is the image data of the icon indicating thecurrent geographic location of Device A on the map data. Device B IconImage Data Storage Area H552 b 5 b stores the Device B icon image datawhich is the image data of the icon indicating the current geographiclocation of Device B on the map data.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area H552 b 6. In this embodiment, PartyLocation Notifying Data Storage Area H552 b 6 includes Device A LocationNotifying Data Storage Area H552 b 6 a and Device B Location NotifyingData Storage Area H552 b 6 b. Device A Location Notifying Data StorageArea H552 b 6 a stores the Device A location notifying data which is theaudiovisual data notifying that the current geographic location ofDevice A is notified. Device B Location Notifying Data Storage Area H552b 6 b stores the Device B location notifying data which is theaudiovisual data notifying that the current geographic location ofDevice B is notified.

This paragraph illustrates the software program(s) stored in ZoneLeaving Notifying Software Storage Area H552 c. In this embodiment, ZoneLeaving Notifying Software Storage Area H552 c stores 1st Zone DataProducing Software H552 c 1, 2nd Zone Data Producing Software H552 c 2,3rd Zone Data Producing Software H552 c 3, 4th Zone Data ProducingSoftware H552 c 4, Device A Location Data Producing Software H552 c 5,1st Zone Leaving Notice Data Outputting Software H552 c 7, 2nd ZoneLeaving Notice Data Outputting Software H552 c 8, 3rd Zone LeavingNotice Data Outputting Software H552 c 9, and 4th Zone Leaving NoticeData Outputting Software H552 c 10. 1st Zone Data Producing SoftwareH552 c 1 is the software program described hereinafter. 2nd Zone DataProducing Software H552 c 2 is the software program describedhereinafter. 3rd Zone Data Producing Software H552 c 3 is the softwareprogram described hereinafter. 4th Zone Data Producing Software H552 c 4is the software program described hereinafter. Device A Location DataProducing Software H552 c 5 is the software program describedhereinafter. 1st Zone Leaving Notice Data Outputting Software H552 c 7is the software program described hereinafter. 2nd Zone Leaving NoticeData Outputting Software H552 c 8 is the software program describedhereinafter. 3rd Zone Leaving Notice Data Outputting Software H552 c 9is the software program described hereinafter. 4th Zone Leaving NoticeData Outputting Software H552 c 10 is the software program describedhereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device A. In this embodiment, RAM 206 includes Zone Leaving NotifyingInformation Storage Area 206A552 a of which the data and the softwareprogram(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device A.

This paragraph illustrates the storage area(s) included in Zone LeavingNotifying Information Storage Area 206A552 a. In this embodiment, ZoneLeaving Notifying Information Storage Area 206A552 a includes ZoneLeaving Notifying Data Storage Area 206A552 b and Zone Leaving NotifyingSoftware Storage Area 206A552 c. Zone Leaving Notifying Data StorageArea 206A552 b stores the data necessary to implement the presentfunction on the side of Device A, such as the one(s) describedhereinafter. Zone Leaving Notifying Software Storage Area 206A552 cstores the software program(s) necessary to implement the presentfunction on the side of Device A, such as the one(s) describedhereinafter.

This paragraph illustrates the storage area(s) included in Zone LeavingNotifying Data Storage Area 206A552 b. In this embodiment, Zone LeavingNotifying Data Storage Area 206A552 b includes Map Data Storage Area206A552 b 1, Party Zone Data Storage Area 206A552 b 2, Party LocationData Storage Area 206A552 b 3, Party Zone Leaving Notice Data StorageArea 206A552 b 4, Party Icon Image Data Storage Area 206A552 b 5, PartyLocation Notifying Data Storage Area 206A552 b 6, and Work Area 206A552b 7. Map Data Storage Area 206A552 b 1 stores the map data which is theimage data indicating a map. Party Zone Data Storage Area 206A552 b 2stores the data described hereinafter. Party Location Data Storage Area206A552 b 3 stores the data described hereinafter. Party Zone LeavingNotice Data Storage Area 206A552 b 4 stores the data describedhereinafter. Party Icon Image Data Storage Area 206A552 b 5 stores thedata described hereinafter. Party Location Notifying Data Storage Area206A552 b 6 stores the data described hereinafter. Work Area 206A552 b 7is utilized as a work area to perform calculation and temporarily storedata.

This paragraph illustrates the storage area(s) included in Party ZoneData Storage Area 206A552 b 2. In this embodiment, Party Zone DataStorage Area 206A552 b 2 includes 1st Zone Data Storage Area 206A552 b 2a, 2nd Zone Data Storage Area 206A552 b 2 b, 3rd Zone Data Storage Area206A552 b 2 c, and 4th Zone Data Storage Area 206A552 b 2 d. 1st ZoneData Storage Area 206A552 b 2 a stores the 1st zone data which indicatesa certain geographic zone or area. 2nd Zone Data Storage Area 206A552 b2 b stores the 2nd zone data which indicates a certain geographic zoneor area. 3rd Zone Data Storage Area 206A552 b 2 c stores the 3rd zonedata which indicates a certain geographic zone or area. 4th Zone DataStorage Area 206A552 b 2 d stores the 4th zone data which indicates acertain geographic zone or area.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area 206A552 b 3. In this embodiment, PartyLocation Data Storage Area 206A552 b 3 includes Device A Location DataStorage Area 206A552 b 3 a and Device B Location Data Storage Area206A552 b 3 b. Device A Location Data Storage Area 206A552 b 3 a storesthe Device A location data which indicates the current geographiclocation of Device A in (x,y,z) format. Device B Location Data StorageArea 206A552 b 3 b stores the Device B location data which indicates thecurrent geographic location of Device B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in Party ZoneLeaving Notice Data Storage Area 206A552 b 4. In this embodiment, PartyZone Leaving Notice Data Storage Area 206A552 b 4 includes 1st ZoneLeaving Notice Data Storage Area 206A552 b 4 a, 2nd Zone Leaving NoticeData Storage Area 206A552 b 4 b, 3rd Zone Leaving Notice Data StorageArea 206A552 b 4 c, and 4th Zone Leaving Notice Data Storage Area206A552 b 4 d. 1st Zone Leaving Notice Data Storage Area 206A552 b 4 astores the 1st zone leaving notice data which is the audiovisual dataindicating that Device A left the zone indicated by the 1st zone data.2nd Zone Leaving Notice Data Storage Area 206A552 b 4 b stores the 2ndzone leaving notice data which is the audiovisual data indicating thatDevice A left the zone indicated by the 2nd zone data. 3rd Zone LeavingNotice Data Storage Area 206A552 b 4 c stores the 3rd zone leavingnotice data which is the audiovisual data indicating that Device B leftthe zone indicated by the 3rd zone data. 4th Zone Leaving Notice DataStorage Area 206A552 b 4 d stores the 4th zone leaving notice data whichis the audiovisual data indicating that Device B left the zone indicatedby the 4th zone data.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area 206A552 b 5. In this embodiment, Party IconImage Data Storage Area 206A552 b 5 includes Device A Icon Image DataStorage Area 206A552 b 5 a and Device B Icon Image Data Storage Area206A552 b 5 b. Device A Icon Image Data Storage Area 206A552 b 5 astores the Device A icon image data which is the image data of the iconindicating the current geographic location of Device A on the map data.Device B Icon Image Data Storage Area 206A552 b 5 b stores the Device Bicon image data which is the image data of the icon indicating thecurrent geographic location of Device B on the map data.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area 206A552 b 6. In this embodiment,Party Location Notifying Data Storage Area 206A552 b 6 includes Device ALocation Notifying Data Storage Area 206A552 b 6 a and Device B LocationNotifying Data Storage Area 206A552 b 6 b. Device A Location NotifyingData Storage Area 206A552 b 6 a stores the Device A location notifyingdata which is the audiovisual data notifying that the current geographiclocation of Device A is notified. Device B Location Notifying DataStorage Area 206A552 b 6 b stores the Device B location notifying datawhich is the audiovisual data notifying that the current geographiclocation of Device B is notified.

This paragraph illustrates the software program(s) stored in ZoneLeaving Notifying Software Storage Area 206A552 c. In this embodiment,Zone Leaving Notifying Software Storage Area 206A552 c stores 1st ZoneData Producing Software 206A552 c 1, 2nd Zone Data Producing Software206A552 c 2, 3rd Zone Data Producing Software 206A552 c 3, 4th Zone DataProducing Software 206A552 c 4, Device A Location Data ProducingSoftware 206A552 c 5, 1st Zone Leaving Notice Data Outputting Software206A552 c 7, 2nd Zone Leaving Notice Data Outputting Software 206A552 c8, 3rd Zone Leaving Notice Data Outputting Software 206A552 c 9, and 4thZone Leaving Notice Data Outputting Software 206A552 c 10. 1st Zone DataProducing Software 206A552 c 1 is the software program describedhereinafter. 2nd Zone Data Producing Software 206A552 c 2 is thesoftware program described hereinafter. 3rd Zone Data Producing Software206A552 c 3 is the software program described hereinafter. 4th Zone DataProducing Software 206A552 c 4 is the software program describedhereinafter. Device A Location Data Producing Software 206A552 c 5 isthe software program described hereinafter. 1st Zone Leaving Notice DataOutputting Software 206A552 c 7 is the software program describedhereinafter. 2nd Zone Leaving Notice Data Outputting Software 206A552 c8 is the software program described hereinafter. 3rd Zone Leaving NoticeData Outputting Software 206A552 c 9 is the software program describedhereinafter. 4th Zone Leaving Notice Data Outputting Software 206A552 c10 is the software program described hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device B. In this embodiment, RAM 206 includes Zone Leaving NotifyingInformation Storage Area 206B552 a of which the data and the softwareprogram(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device B.

This paragraph illustrates the storage area(s) included in Zone LeavingNotifying Information Storage Area 206B552 a. In this embodiment, ZoneLeaving Notifying Information Storage Area 206B552 a includes ZoneLeaving Notifying Data Storage Area 206B552 b and Zone Leaving NotifyingSoftware Storage Area 206B552 c. Zone Leaving Notifying Data StorageArea 206B552 b stores the data necessary to implement the presentfunction on the side of Device B, such as the one(s) describedhereinafter. Zone Leaving Notifying Software Storage Area 206B552 cstores the software program(s) necessary to implement the presentfunction on the side of Device B, such as the one(s) describedhereinafter.

This paragraph illustrates the storage area(s) included in Zone LeavingNotifying Data Storage Area 206B552 b. In this embodiment, Zone LeavingNotifying Data Storage Area 206B552 b includes Map Data Storage Area206B552 b 1, Party Zone Data Storage Area 206B552 b 2, Party LocationData Storage Area 206B552 b 3, Party Zone Leaving Notice Data StorageArea 206B552 b 4, Party Icon Image Data Storage Area 206B552 b 5, PartyLocation Notifying Data Storage Area 206B552 b 6, and Work Area 206B552b 7. Map Data Storage Area 206B552 b 1 stores the map data which is theimage data indicating a map. Party Zone Data Storage Area 206B552 b 2stores the data described hereinafter. Party Location Data Storage Area206B552 b 3 stores the data described hereinafter. Party Zone LeavingNotice Data Storage Area 206B552 b 4 stores the data describedhereinafter. Party Icon Image Data Storage Area 206B552 b 5 stores thedata described hereinafter. Party Location Notifying Data Storage Area206B552 b 6 stores the data described hereinafter. Work Area 206B552 b 7is utilized as a work area to perform calculation and temporarily storedata.

This paragraph illustrates the storage area(s) included in Party ZoneData Storage Area 206B552 b 2. In this embodiment, Party Zone DataStorage Area 206B552 b 2 includes 1st Zone Data Storage Area 206B552 b 2a, 2nd Zone Data Storage Area 206B552 b 2 b, 3rd Zone Data Storage Area206B552 b 2 c, and 4th Zone Data Storage Area 206B552 b 2 d. 1st ZoneData Storage Area 206B552 b 2 a stores the 1st zone data which indicatesa certain geographic zone or area. 2nd Zone Data Storage Area 206B552 b2 b stores the 2nd zone data which indicates a certain geographic zoneor area. 3rd Zone Data Storage Area 206B552 b 2 c stores the 3rd zonedata which indicates a certain geographic zone or area. 4th Zone DataStorage Area 206B552 b 2 d stores the 4th zone data which indicates acertain geographic zone or area.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area 206B552 b 3. In this embodiment, PartyLocation Data Storage Area 206B552 b 3 includes Device A Location DataStorage Area 206B552 b 3 a and Device B Location Data Storage Area206B552 b 3 b. Device A Location Data Storage Area 206B552 b 3 a storesthe Device A location data which indicates the current geographiclocation of Device A in (x,y,z) format. Device B Location Data StorageArea 206B552 b 3 b stores the Device B location data which indicates thecurrent geographic location of Device B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in Party ZoneLeaving Notice Data Storage Area 206B552 b 4. In this embodiment, PartyZone Leaving Notice Data Storage Area 206B552 b 4 includes 1st ZoneLeaving Notice Data Storage Area 206B552 b 4 a, 2nd Zone Leaving NoticeData Storage Area 206B552 b 4 b, 3rd Zone Leaving Notice Data StorageArea 206B552 b 4 c, and 4th Zone Leaving Notice Data Storage Area206B552 b 4 d. 1st Zone Leaving Notice Data Storage Area 206B552 b 4 astores the 1st zone leaving notice data which is the audiovisual dataindicating that Device A left the zone indicated by the 1st zone data.2nd Zone Leaving Notice Data Storage Area 206B552 b 4 b stores the 2ndzone leaving notice data which is the audiovisual data indicating thatDevice A left the zone indicated by the 2nd zone data. 3rd Zone LeavingNotice Data Storage Area 206B552 b 4 c stores the 3rd zone leavingnotice data which is the audiovisual data indicating that Device B leftthe zone indicated by the 3rd zone data. 4th Zone Leaving Notice DataStorage Area 206B552 b 4 d stores the 4th zone leaving notice data whichis the audiovisual data indicating that Device B left the zone indicatedby the 4th zone data.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area 206B552 b 5. In this embodiment, Party IconImage Data Storage Area 206B552 b 5 includes Device A Icon Image DataStorage Area 206B552 b 5 a and Device B Icon Image Data Storage Area206B552 b 5 b. Device A Icon Image Data Storage Area 206B552 b 5 astores the Device A icon image data which is the image data of the iconindicating the current geographic location of Device A on the map data.Device B Icon Image Data Storage Area 206B552 b 5 b stores the Device Bicon image data which is the image data of the icon indicating thecurrent geographic location of Device B on the map data.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area 206B552 b 6. In this embodiment,Party Location Notifying Data Storage Area 206B552 b 6 includes Device ALocation Notifying Data Storage Area 206B552 b 6 a and Device B LocationNotifying Data Storage Area 206B552 b 6 b. Device A Location NotifyingData Storage Area 206B552 b 6 a stores the Device A location notifyingdata which is the audiovisual data notifying that the current geographiclocation of Device A is notified. Device B Location Notifying DataStorage Area 206B552 b 6 b stores the Device B location notifying datawhich is the audiovisual data notifying that the current geographiclocation of Device B is notified.

This paragraph illustrates the software program(s) stored in ZoneLeaving Notifying Software Storage Area 206B552 c. In this embodiment,Zone Leaving Notifying Software Storage Area 206B552 c stores 1st ZoneData Producing Software 206B552 c 1, 2nd Zone Data Producing Software206B552 c 2, 3rd Zone Data Producing Software 206B552 c 3, 4th Zone DataProducing Software 206B552 c 4, Device B Location Data ProducingSoftware 206B552 c 6, 1st Zone Leaving Notice Data Outputting Software206B552 c 7, 2nd Zone Leaving Notice Data Outputting Software 206B552 c8, 3rd Zone Leaving Notice Data Outputting Software 206B552 c 9, and 4thZone Leaving Notice Data Outputting Software 206B552 c 10. 1st Zone DataProducing Software 206B552 c 1 is the software program describedhereinafter. 2nd Zone Data Producing Software 206B552 c 2 is thesoftware program described hereinafter. 3rd Zone Data Producing Software206B552 c 3 is the software program described hereinafter. 4th Zone DataProducing Software 206B552 c 4 is the software program describedhereinafter. Device B Location Data Producing Software 206B552 c 6 isthe software program described hereinafter. 1st Zone Leaving Notice DataOutputting Software 206B552 c 7 is the software program describedhereinafter. 2nd Zone Leaving Notice Data Outputting Software 206B552 c8 is the software program described hereinafter. 3rd Zone Leaving NoticeData Outputting Software 206B552 c 9 is the software program describedhereinafter. 4th Zone Leaving Notice Data Outputting Software 206B552 c10 is the software program described hereinafter.

This paragraph illustrate(s) 1st Zone Data Producing Software H552 c 1of Host H and 1st Zone Data Producing Software 206A552 c 1 of Device A,which produce(s) the 1st zone data. In this embodiment, Host H retrievesthe map data from Map Data Storage Area H552 b 1 and sends the data toDevice A (S1). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S2). The user of Device A selects, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, a specific zone onthe map data displayed in the previous step (S3). CPU 211 (FIG. 1) ofDevice A produces the 1st zone data by referring to the specific zoneselected in the previous step and sends the data to Host H in a wirelessfashion (S4). Host H receives the 1st zone data from Device A and storesthe data in 1st Zone Data Storage Area H552 b 2 a (S5).

This paragraph illustrate(s) 2nd Zone Data Producing Software H552 c 2of Host H and 2nd Zone Data Producing Software 206A552 c 2 of Device A,which produce(s) the 2nd zone data. In this embodiment, Host H retrievesthe map data from Map Data Storage Area H552 b 1 and sends the data toDevice A (S1). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S2). The user of Device A selects, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, a specific zone onthe map data displayed in the previous step (S3). CPU 211 (FIG. 1) ofDevice A produces the 2nd zone data by referring to the specific zoneselected in the previous step and sends the data to Host H in a wirelessfashion (S4). Host H receives the 2nd zone data from Device A and storesthe data in 2nd Zone Data Storage Area H552 b 2 b (S5).

This paragraph illustrate(s) 3rd Zone Data Producing Software H552 c 3of Host H and 3rd Zone Data Producing Software 206A552 c 3 of Device A,which produce(s) the 3rd zone data. In this embodiment, Host H retrievesthe map data from Map Data Storage Area H552 b 1 and sends the data toDevice A (S1). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S2). The user of Device A selects, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, a specific zone onthe map data displayed in the previous step (S3). CPU 211 (FIG. 1) ofDevice A produces the 3rd zone data by referring to the specific zoneselected in the previous step and sends the data to Host H in a wirelessfashion (S4). Host H receives the 3rd zone data from Device A and storesthe data in 3rd Zone Data Storage Area H552 b 2 c (S5).

This paragraph illustrate(s) 4th Zone Data Producing Software H552 c 4of Host H and 4th Zone Data Producing Software 206A552 c 4 of Device A,which produce(s) the 4th zone data. In this embodiment, Host H retrievesthe map data from Map Data Storage Area H552 b 1 and sends the data toDevice A (S1). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S2). The user of Device A selects, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, a specific zone onthe map data displayed in the previous step (S3). CPU 211 (FIG. 1) ofDevice A produces the 4th zone data by referring to the specific zoneselected in the previous step and sends the data to Host H in a wirelessfashion (S4). Host H receives the 4th zone data from Device A and storesthe data in 4th Zone Data Storage Area H552 b 2 d (S5).

This paragraph illustrate(s) 1st Zone Data Producing Software 206B552 c₁ of Device B, which produce(s) the 1st zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B552 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 1st zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 1st zonedata produced in the previous step in 1st Zone Data Storage Area 206B552b 2 a (S5).

This paragraph illustrate(s) 2nd Zone Data Producing Software 206B552 c2 of Device B, which produce(s) the 2nd zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B552 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 2nd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 2nd zonedata produced in the previous step in 2nd Zone Data Storage Area 206B552b 2 b (S5).

This paragraph illustrate(s) 3rd Zone Data Producing Software 206B552 c3 of Device B, which produce(s) the 3rd zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B552 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 3rd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 3rd zonedata produced in the previous step in 3rd Zone Data Storage Area 206B552b 2 c (S5).

This paragraph illustrate(s) 4th Zone Data Producing Software 206B552 c4 of Device B, which produce(s) the 4th zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B552 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 4th zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 4th zonedata produced in the previous step in 4th Zone Data Storage Area 206B552b 2 d (S5).

This paragraph illustrate(s) Device A Location Data Producing SoftwareH552 c 5 of Host H and Device A Location Data Producing Software 206A552c 5 of Device A, which produce(s) Device A location data. In thisembodiment, CPU 211 (FIG. 1) of Device A identifies the current locationof Device A (S1). CPU 211 (FIG. 1) of Device A produces the Device Alocation data by utilizing the current location identified in theprevious step and sends the data to Host H in a wireless fashion (S2).Host H receives the Device A location data from Device A and stores thedata in Device A Location Data Storage Area H552 b 3 a (S3). Theforegoing sequence is repeated periodically.

This paragraph illustrate(s) Device B Location Data Producing Software206B552 c 6 of Device B, which produce(s) Device B location data. Inthis embodiment, CPU 211 (FIG. 1) of Device B identifies the currentlocation of Device B (S1). CPU 211 (FIG. 1) of Device B produces theDevice B location data by utilizing the current location identified inthe previous step (S2). CPU 211 (FIG. 1) of Device B stores the Device Blocation data produced in the previous step in Device B Location DataStorage Area 206B552 b 3 b (S3). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 1st Zone Leaving Notice Data OutputtingSoftware H552 c 7 of Host H, 1st Zone Leaving Notice Data OutputtingSoftware 206A552 c 7 of Device A, and 1st Zone Leaving Notice DataOutputting Software 206B552 c 7 of Device B, which output(s) the 1stzone leaving notice data. In this embodiment, Host H retrieves theDevice A location data from Device A Location Data Storage Area H552 b 3a (S1). Host H retrieves the 1st zone data from 1st Zone Data StorageArea H552 b 2 a (S2). If the Device A location data retrieved in S1 islocated outside of the 1st zone data retrieved in the previous step,Host H proceeds to the next step (S3). Host H retrieves the 1st zoneleaving notice data from 1st Zone Leaving Notice Data Storage Area H552b 4 a and sends the data to Device A (S4). CPU 211 (FIG. 1) of Device Areceives the 1st zone leaving notice data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S5). Host H sends the Device B location datatransferring request to Device B (S6). Here, the Device B location datatransferring request is the request to transfer the Device B locationdata. CPU 211 (FIG. 1) of Device B receives the Device B location datatransferring request from Host H in a wireless fashion (S7). CPU 211(FIG. 1) of Device B retrieves the Device B location data from Device BLocation Data Storage Area 206B552 b 3 b and sends the data to Host H ina wireless fashion (S8). Host H receives the Device B location data fromDevice B and stores the data in Device B Location Data Storage Area H552b 3 b (S9). Host H retrieves the map data from Map Data Storage AreaH552 b 1 and sends the data to Device A (S10). CPU 211 (FIG. 1) ofDevice A receives the map data from Host H in a wireless fashion anddisplays the data on LCD 201 (FIG. 1) of Device A (S11). Host Hretrieves the Device A location data from Device A Location Data StorageArea H552 b 3 a and sends the data to Device A (S12). CPU 211 (FIG. 1)of Device A receives the Device A location data from Host H in awireless fashion (S13). Host H retrieves the Device A icon image datafrom Device A Icon Image Data Storage Area H552 b 5 a and sends the datato Device A (S14). CPU 211 (FIG. 1) of Device A receives the Device Aicon image data from Host H in a wireless fashion (S15). CPU 211(FIG. 1) of Device A displays the Device A icon image data received inthe previous step at the location corresponding to the Device A locationdata received in S13 on the map data displayed in S11 (S16). Host Hretrieves the Device B location data from Device B Location Data StorageArea H552 b 3 b and sends the data to Device A (S17). CPU 211 (FIG. 1)of Device A receives the Device B location data from Host H in awireless fashion (S18). Host H retrieves the Device B icon image datafrom Device B Icon Image Data Storage Area H552 b 5 b and sends the datato Device A (S19). CPU 211 (FIG. 1) of Device A receives the Device Bicon image data from Host H in a wireless fashion (S20). CPU 211(FIG. 1) of Device A displays the Device B icon image data received inthe previous step at the location corresponding to the Device B locationdata received in S18 on the map data displayed in S11 (S21). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Zone Leaving Notice Data OutputtingSoftware H552 c 8 of Host H, 2nd Zone Leaving Notice Data OutputtingSoftware 206A552 c 8 of Device A, and 2nd Zone Leaving Notice DataOutputting Software 206B552 c 8 of Device B, which output(s) the 2ndzone leaving notice data. In this embodiment, Host H retrieves theDevice A location data from Device A Location Data Storage Area H552 b 3a (S1). Host H retrieves the 2nd zone data from 2nd Zone Data StorageArea H552 b 2 b (S2). If the Device A location data retrieved in S1 islocated outside of the 2nd zone data retrieved in the previous step,Host H proceeds to the next step (S3). Host H retrieves the 2nd zoneleaving notice data from 2nd Zone Leaving Notice Data Storage Area H552b 4 b and sends the data to Device A (S4). CPU 211 (FIG. 1) of Device Areceives the 2nd zone leaving notice data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S5). Host H sends the Device B location datatransferring request to Device B (S6). Here, the Device B location datatransferring request is the request to transfer the Device B locationdata. CPU 211 (FIG. 1) of Device B receives the Device B location datatransferring request from Host H in a wireless fashion (S7). CPU 211(FIG. 1) of Device B retrieves the Device B location data from Device BLocation Data Storage Area 206B552 b 3 b and sends the data to Host H ina wireless fashion (S8). Host H receives the Device B location data fromDevice B and stores the data in Device B Location Data Storage Area H552b 3 b (S9). Host H retrieves the map data from Map Data Storage AreaH552 b 1 and sends the data to Device A (S10). CPU 211 (FIG. 1) ofDevice A receives the map data from Host H in a wireless fashion anddisplays the data on LCD 201 (FIG. 1) of Device A (S11). Host Hretrieves the Device A location data from Device A Location Data StorageArea H552 b 3 a and sends the data to Device A (S12). CPU 211 (FIG. 1)of Device A receives the Device A location data from Host H in awireless fashion (S13). Host H retrieves the Device A icon image datafrom Device A Icon Image Data Storage Area H552 b 5 a and sends the datato Device A (S14). CPU 211 (FIG. 1) of Device A receives the Device Aicon image data from Host H in a wireless fashion (S15). CPU 211(FIG. 1) of Device A displays the Device A icon image data received inthe previous step at the location corresponding to the Device A locationdata received in S13 on the map data displayed in S11 (S16). Host Hretrieves the Device B location data from Device B Location Data StorageArea H552 b 3 b and sends the data to Device A (S17). CPU 211 (FIG. 1)of Device A receives the Device B location data from Host H in awireless fashion (S18). Host H retrieves the Device B icon image datafrom Device B Icon Image Data Storage Area H552 b 5 b and sends the datato Device A (S19). CPU 211 (FIG. 1) of Device A receives the Device Bicon image data from Host H in a wireless fashion (S20). CPU 211(FIG. 1) of Device A displays the Device B icon image data received inthe previous step at the location corresponding to the Device B locationdata received in S18 on the map data displayed in S11 (S21). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 3rd Zone Leaving Notice Data OutputtingSoftware H552 c 9 of Host H, 3rd Zone Leaving Notice Data OutputtingSoftware 206A552 c 9 of Device A, and 3rd Zone Leaving Notice DataOutputting Software 206B552 c 9 of Device B, which output(s) the 3rdzone leaving notice data. In this embodiment, Host H sends the Device Blocation data transferring request to Device B (S1). Here, the Device Blocation data transferring request is the request to transfer the DeviceB location data. CPU 211 (FIG. 1) of Device B receives the Device Blocation data transferring request from Host H in a wireless fashion(S2). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B552 b 3 b and sends thedata to Host H in a wireless fashion (S3). Host H receives the Device Blocation data from Device B and stores the data in Device B LocationData Storage Area H552 b 3 b (S4). Host H retrieves the Device Blocation data from Device B Location Data Storage Area H552 b 3 b (S5).Host H retrieves the 3rd zone data from 3rd Zone Data Storage Area H552b 2 c (S6). If the Device B location data retrieved in S5 is locatedoutside of the 3rd zone data retrieved in the previous step, Host Hproceeds to the next step (S7). Host H retrieves the 3rd zone leavingnotice data from 3rd Zone Leaving Notice Data Storage Area H552 b 4 cand sends the data to Device A (S8). CPU 211 (FIG. 1) of Device Areceives the 3rd zone leaving notice data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S9). Host H retrieves the map data from Map DataStorage Area H552 b 1 and sends the data to Device A (S10). CPU 211(FIG. 1) of Device A receives the map data from Host H in a wirelessfashion and displays the data on LCD 201 (FIG. 1) of Device A (S11).Host H retrieves the Device A location data from Device A Location DataStorage Area H552 b 3 a and sends the data to Device A (S12). CPU 211(FIG. 1) of Device A receives the Device A location data from Host H ina wireless fashion (S13). Host H retrieves the Device A icon image datafrom Device A Icon Image Data Storage Area H552 b 5 a and sends the datato Device A (S14). CPU 211 (FIG. 1) of Device A receives the Device Aicon image data from Host H in a wireless fashion (S15). CPU 211(FIG. 1) of Device A displays the Device A icon image data received inthe previous step at the location corresponding to the Device A locationdata received in S13 on the map data displayed in S11 (S16). Host Hretrieves the Device B location data from Device B Location Data StorageArea H552 b 3 b and sends the data to Device A (S17). CPU 211 (FIG. 1)of Device A receives the Device B location data from Host H in awireless fashion (S18). Host H retrieves the Device B icon image datafrom Device B Icon Image Data Storage Area H552 b 5 b and sends the datato Device A (S19). CPU 211 (FIG. 1) of Device A receives the Device Bicon image data from Host H in a wireless fashion (S20). CPU 211(FIG. 1) of Device A displays the Device B icon image data received inthe previous step at the location corresponding to the Device B locationdata received in S18 on the map data displayed in S11 (S21). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 4th Zone Leaving Notice Data OutputtingSoftware H552 c 10 of Host H, 4th Zone Leaving Notice Data OutputtingSoftware 206A552 c 10 of Device A, and 4th Zone Leaving Notice DataOutputting Software 206B552 c ₁₀ of Device B, which output(s) the 4thzone leaving notice data. In this embodiment, Host H sends the Device Blocation data transferring request to Device B (S1). Here, the Device Blocation data transferring request is the request to transfer the DeviceB location data. CPU 211 (FIG. 1) of Device B receives the Device Blocation data transferring request from Host H in a wireless fashion(S2). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B552 b 3 b and sends thedata to Host H in a wireless fashion (S3). Host H receives the Device Blocation data from Device B and stores the data in Device B LocationData Storage Area H552 b 3 b (S4). Host H retrieves the Device Blocation data from Device B Location Data Storage Area H552 b 3 b (S5).Host H retrieves the 4th zone data from 4th Zone Data Storage Area H552b 2 d (S6). If the Device B location data retrieved in S5 is locatedoutside of the 4th zone data retrieved in the previous step, Host Hproceeds to the next step (S7). Host H retrieves the 4th zone leavingnotice data from 4th Zone Leaving Notice Data Storage Area H552 b 4 dand sends the data to Device A (S8). CPU 211 (FIG. 1) of Device Areceives the 4th zone leaving notice data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S9). Host H retrieves the map data from Map DataStorage Area H552 b 1 and sends the data to Device A (S10). CPU 211(FIG. 1) of Device A receives the map data from Host H in a wirelessfashion and displays the data on LCD 201 (FIG. 1) of Device A (S11).Host H retrieves the Device A location data from Device A Location DataStorage Area H552 b 3 a and sends the data to Device A (S12). CPU 211(FIG. 1) of Device A receives the Device A location data from Host H ina wireless fashion (S13). Host H retrieves the Device A icon image datafrom Device A Icon Image Data Storage Area H552 b 5 a and sends the datato Device A (S14). CPU 211 (FIG. 1) of Device A receives the Device Aicon image data from Host H in a wireless fashion (S15). CPU 211(FIG. 1) of Device A displays the Device A icon image data received inthe previous step at the location corresponding to the Device A locationdata received in S13 on the map data displayed in S11 (S16). Host Hretrieves the Device B location data from Device B Location Data StorageArea H552 b 3 b and sends the data to Device A (S17). CPU 211 (FIG. 1)of Device A receives the Device B location data from Host H in awireless fashion (S18). Host H retrieves the Device B icon image datafrom Device B Icon Image Data Storage Area H552 b 5 b and sends the datato Device A (S19). CPU 211 (FIG. 1) of Device A receives the Device Bicon image data from Host H in a wireless fashion (S20). CPU 211(FIG. 1) of Device A displays the Device B icon image data received inthe previous step at the location corresponding to the Device B locationdata received in S18 on the map data displayed in S11 (S21). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 1st Zone Leaving Notice Data OutputtingSoftware H552 c 7 of Host H and 1st Zone Leaving Notice Data OutputtingSoftware 206B552 c 7 of Device B, which output(s) the 1st zone leavingnotice data. In this embodiment, CPU 211 (FIG. 1) of Device B sends theDevice A location data transferring request to Host H in a wirelessfashion (S1). Here, the Device A location data transferring request isthe request to transfer the Device A location data. Host H receives theDevice A location data transferring request from Device B (S2). Host Hretrieves the Device A location data from Device A Location Data StorageArea H552 b 3 a and sends the data to Device B (S3). CPU 211 (FIG. 1) ofDevice B receives the Device A location data from Host H in a wirelessfashion and stores the data in Device A Location Data Storage Area206B552 b 3 a (S4). CPU 211 (FIG. 1) of Device B retrieves the Device Alocation data from Device A Location Data Storage Area 206B552 b 3 a(S5). CPU 211 (FIG. 1) of Device B retrieves the 1st zone data from 1stZone Data Storage Area 206B552 b 2 a (S6). If the Device A location dataretrieved in S5 is located outside of the 1st zone data retrieved in theprevious step, CPU 211 (FIG. 1) of Device B proceeds to the next step(S7). CPU 211 (FIG. 1) of Device B retrieves the 1st zone leaving noticedata from 1st Zone Leaving Notice Data Storage Area 206B552 b 4 a (S8).CPU 211 (FIG. 1) of Device B outputs the 1st zone leaving notice dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device B (S9). CPU 211 (FIG. 1) of Device B retrieves themap data from Map Data Storage Area 206B552 b 1 (S10). CPU 211 (FIG. 1)of Device B displays the map data retrieved in the previous step on LCD201 (FIG. 1) of Device B (S11). CPU 211 (FIG. 1) of Device B retrievesthe Device A location data from Device A Location Data Storage Area206B552 b 3 a (S12). CPU 211 (FIG. 1) of Device B retrieves the Device Aicon image data from Device A Icon Image Data Storage Area 206B552 b 5 a(S13). CPU 211 (FIG. 1) of Device B displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B552 b 3 b (S15). CPU 211(FIG. 1) of Device B retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206B552 b 5 b (S16). CPU 211 (FIG. 1) ofDevice B displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Zone Leaving Notice Data OutputtingSoftware H552 c 8 of Host H and 2nd Zone Leaving Notice Data OutputtingSoftware 206B552 c 8 of Device B, which output(s) the 2nd zone leavingnotice data. In this embodiment, CPU 211 (FIG. 1) of Device B sends theDevice A location data transferring request to Host H in a wirelessfashion (S1). Here, the Device A location data transferring request isthe request to transfer the Device A location data. Host H receives theDevice A location data transferring request from Device B (S2). Host Hretrieves the Device A location data from Device A Location Data StorageArea H552 b 3 a and sends the data to Device B (S3). CPU 211 (FIG. 1) ofDevice B receives the Device A location data from Host H in a wirelessfashion and stores the data in Device A Location Data Storage Area206B552 b 3 a (S4). CPU 211 (FIG. 1) of Device B retrieves the Device Alocation data from Device A Location Data Storage Area 206B552 b 3 a(S5). CPU 211 (FIG. 1) of Device B retrieves the 2nd zone data from 2ndZone Data Storage Area 206B552 b 2 b (S6). If the Device A location dataretrieved in S5 is located outside of the 2nd zone data retrieved in theprevious step, CPU 211 (FIG. 1) of Device B proceeds to the next step(S7). CPU 211 (FIG. 1) of Device B retrieves the 2nd zone leaving noticedata from 2nd Zone Leaving Notice Data Storage Area 206B552 b 4 b (S8).CPU 211 (FIG. 1) of Device B outputs the 2nd zone leaving notice dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device B (S9). CPU 211 (FIG. 1) of Device B retrieves themap data from Map Data Storage Area 206B552 b 1 (S10). CPU 211 (FIG. 1)of Device B displays the map data retrieved in the previous step on LCD201 (FIG. 1) of Device B (S11). CPU 211 (FIG. 1) of Device B retrievesthe Device A location data from Device A Location Data Storage Area206B552 b 3 a (S12). CPU 211 (FIG. 1) of Device B retrieves the Device Aicon image data from Device A Icon Image Data Storage Area 206B552 b 5 a(S13). CPU 211 (FIG. 1) of Device B displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B552 b 3 b (S15). CPU 211(FIG. 1) of Device B retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206B552 b 5 b (S16). CPU 211 (FIG. 1) ofDevice B displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 3rd Zone Leaving Notice Data OutputtingSoftware H552 c 9 of Host H and 3rd Zone Leaving Notice Data OutputtingSoftware 206B552 c 9 of Device B, which output(s) the 3rd zone leavingnotice data. In this embodiment, CPU 211 (FIG. 1) of Device B retrievesthe Device B location data from Device B Location Data Storage Area206B552 b 3 b (S1). CPU 211 (FIG. 1) of Device B retrieves the 3rd zonedata from 3rd Zone Data Storage Area 206B552 b 2 c (S2). If the Device Blocation data retrieved in 51 is located outside of the 3rd zone dataretrieved in the previous step, CPU 211 (FIG. 1) of Device B proceeds tothe next step (S3). CPU 211 (FIG. 1) of Device B retrieves the 3rd zoneleaving notice data from 3rd Zone Leaving Notice Data Storage Area206B552 b 4 c (S4). CPU 211 (FIG. 1) of Device B outputs the 3rd zoneleaving notice data retrieved in the previous step from Speaker 216(FIG. 1) and LCD 201 (FIG. 1) of Device B (S5). CPU 211 (FIG. 1) ofDevice B retrieves the map data from Map Data Storage Area 206B552 b 1(S6). CPU 211 (FIG. 1) of Device B displays the map data retrieved inthe previous step on LCD 201 (FIG. 1) of Device B (S7). CPU 211 (FIG. 1)of Device B sends the Device A location data transferring request toHost H in a wireless fashion (S8). Here, the Device A location datatransferring request is the request to transfer the Device A locationdata. Host H receives the Device A location data transferring requestfrom Device B (S9). Host H retrieves the Device A location data fromDevice A Location Data Storage Area H552 b 3 a and sends the data toDevice B (S10). CPU 211 (FIG. 1) of Device B receives the Device Alocation data from Host H in a wireless fashion and stores the data inDevice A Location Data Storage Area 206B552 b 3 a (S11). CPU 211(FIG. 1) of Device B retrieves the Device A location data from Device ALocation Data Storage Area 206B552 b 3 a (S12). CPU 211 (FIG. 1) ofDevice B retrieves the Device A icon image data from Device A Icon ImageData Storage Area 206B552 b 5 a (S13). CPU 211 (FIG. 1) of Device Bdisplays the Device A icon image data retrieved in the previous step atthe location corresponding to the Device A location data retrieved inS12 on the map data displayed in S7 (S14). CPU 211 (FIG. 1) of Device Bretrieves the Device B location data from Device B Location Data StorageArea 206B552 b 3 b (S15). CPU 211 (FIG. 1) of Device B retrieves theDevice B icon image data from Device B Icon Image Data Storage Area206B552 b 5 b (S16). CPU 211 (FIG. 1) of Device B displays the Device Bicon image data retrieved in the previous step at the locationcorresponding to the Device B location data retrieved in S15 on the mapdata displayed in S7 (S17). Thus, the current geographic locations ofDevice A and Device B are displayed simultaneously on the map data. Theforegoing sequence is repeated periodically.

This paragraph illustrate(s) 4th Zone Leaving Notice Data OutputtingSoftware H552 c 10 of Host H and 4th Zone Leaving Notice Data OutputtingSoftware 206B552 c 10 of Device B, which output(s) the 4th zone leavingnotice data. In this embodiment, CPU 211 (FIG. 1) of Device B retrievesthe Device B location data from Device B Location Data Storage Area206B552 b 3 b (S1). CPU 211 (FIG. 1) of Device B retrieves the 4th zonedata from 4th Zone Data Storage Area 206B552 b 2 d (S2). If the Device Blocation data retrieved in S1 is located outside of the 4th zone dataretrieved in the previous step, CPU 211 (FIG. 1) of Device B proceeds tothe next step (S3). CPU 211 (FIG. 1) of Device B retrieves the 4th zoneleaving notice data from 4th Zone Leaving Notice Data Storage Area206B552 b 4 d (S4). CPU 211 (FIG. 1) of Device B outputs the 4th zoneleaving notice data retrieved in the previous step from Speaker 216(FIG. 1) and LCD 201 (FIG. 1) of Device B (S5). CPU 211 (FIG. 1) ofDevice B retrieves the map data from Map Data Storage Area 206B552 b 1(S6). CPU 211 (FIG. 1) of Device B displays the map data retrieved inthe previous step on LCD 201 (FIG. 1) of Device B (S7). CPU 211 (FIG. 1)of Device B sends the Device A location data transferring request toHost H in a wireless fashion (S8). Here, the Device A location datatransferring request is the request to transfer the Device A locationdata. Host H receives the Device A location data transferring requestfrom Device B (S9). Host H retrieves the Device A location data fromDevice A Location Data Storage Area H552 b 3 a and sends the data toDevice B (S10). CPU 211 (FIG. 1) of Device B receives the Device Alocation data from Host H in a wireless fashion and stores the data inDevice A Location Data Storage Area 206B552 b 3 a (S11). CPU 211(FIG. 1) of Device B retrieves the Device A location data from Device ALocation Data Storage Area 206B552 b 3 a (S12). CPU 211 (FIG. 1) ofDevice B retrieves the Device A icon image data from Device A Icon ImageData Storage Area 206B552 b 5 a (S13). CPU 211 (FIG. 1) of Device Bdisplays the Device A icon image data retrieved in the previous step atthe location corresponding to the Device A location data retrieved inS12 on the map data displayed in S7 (S14). CPU 211 (FIG. 1) of Device Bretrieves the Device B location data from Device B Location Data StorageArea 206B552 b 3 b (S15). CPU 211 (FIG. 1) of Device B retrieves theDevice B icon image data from Device B Icon Image Data Storage Area206B552 b 5 b (S16). CPU 211 (FIG. 1) of Device B displays the Device Bicon image data retrieved in the previous step at the locationcorresponding to the Device B location data retrieved in S15 on the mapdata displayed in S7 (S17). Thus, the current geographic locations ofDevice A and Device B are displayed simultaneously on the map data. Theforegoing sequence is repeated periodically.

The following paragraphs illustrate another embodiment wherein Device Aplays the major role in implementing the present function.

This paragraph illustrate(s) 1st Zone Data Producing Software 206A552 c1 of Device A, which produces) the 1st zone data. In this embodiment,CPU 211 (FIG. 1) of Device A retrieves the map data from Map DataStorage Area 206A552 b 1 (S1). CPU 211 (FIG. 1) of Device A displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Aproduces the 1st zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device A stores the 1st zonedata produced in the previous step in 1st Zone Data Storage Area 206A552b 2 a (S5).

This paragraph illustrate(s) 2nd Zone Data Producing Software 206A552 c2 of Device A, which produces) the 2nd zone data. In this embodiment,CPU 211 (FIG. 1) of Device A retrieves the map data from Map DataStorage Area 206A552 b 1 (S1). CPU 211 (FIG. 1) of Device A displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Aproduces the 2nd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device A stores the 2nd zonedata produced in the previous step in 2nd Zone Data Storage Area 206A552b 2 b (S5).

This paragraph illustrate(s) 3rd Zone Data Producing Software 206A552 c3 of Device A, which produces) the 3rd zone data. In this embodiment,CPU 211 (FIG. 1) of Device A retrieves the map data from Map DataStorage Area 206A552 b 1 (S1). CPU 211 (FIG. 1) of Device A displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Aproduces the 3rd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device A stores the 3rd zonedata produced in the previous step in 3rd Zone Data Storage Area 206A552b 2 c (S5).

This paragraph illustrate(s) 4th Zone Data Producing Software 206A552 c4 of Device A, which produce(s) the 4th zone data. In this embodiment,CPU 211 (FIG. 1) of Device A retrieves the map data from Map DataStorage Area 206A552 b 1 (S1). CPU 211 (FIG. 1) of Device A displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Aproduces the 4th zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device A stores the 4th zonedata produced in the previous step in 4th Zone Data Storage Area 206A552b 2 d (S5).

This paragraph illustrate(s) 1st Zone Data Producing Software 206B552 c1 of Device B, which produce(s) the 1st zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B552 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 1st zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 1st zonedata produced in the previous step in 1st Zone Data Storage Area 206B552b 2 a (S5).

This paragraph illustrate(s) 2nd Zone Data Producing Software 206B552 c2 of Device B, which produce(s) the 2nd zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B552 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 2nd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 2nd zonedata produced in the previous step in 2nd Zone Data Storage Area 206B552b 2 b (S5).

This paragraph illustrate(s) 3rd Zone Data Producing Software 206B552 c3 of Device B, which produce(s) the 3rd zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B552 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 3rd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 3rd zonedata produced in the previous step in 3rd Zone Data Storage Area 206B552b 2 c (S5).

This paragraph illustrate(s) 4th Zone Data Producing Software 206B552 c4 of Device B, which produce(s) the 4th zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B552 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 4th zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 4th zonedata produced in the previous step in 4th Zone Data Storage Area 206B552b 2 d (S5).

This paragraph illustrate(s) Device A Location Data Producing Software206A552 c 5 of Device A, which produce(s) Device A location data. Inthis embodiment, CPU 211 (FIG. 1) of Device A identifies the currentlocation of Device A (S1). CPU 211 (FIG. 1) of Device A produces theDevice A location data by utilizing the current location identified inthe previous step (S2). CPU 211 (FIG. 1) of Device A stores the Device Alocation data produced in the previous step in Device A Location DataStorage Area 206A552 b 3 a (S3). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) Device B Location Data Producing Software206B552 c 6 of Device B, which produce(s) Device B location data. Inthis embodiment, CPU 211 (FIG. 1) of Device B identifies the currentlocation of Device B (S1). CPU 211 (FIG. 1) of Device B produces theDevice B location data by utilizing the current location identified inthe previous step (S2). CPU 211 (FIG. 1) of Device B stores the Device Blocation data produced in the previous step in Device B Location DataStorage Area 206B552 b 3 b (S3). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 1st Zone Leaving Notice Data OutputtingSoftware 206A552 c 7 of Device A and 1st Zone Leaving Notice DataOutputting Software 206B552 c 7 of Device B, which output(s) the 1stzone leaving notice data. In this embodiment, CPU 211 (FIG. 1) of DeviceA retrieves the Device A location data from Device A Location DataStorage Area 206A552 b 3 a (S1). CPU 211 (FIG. 1) of Device A retrievesthe 1st zone data from 1st Zone Data Storage Area 206A552 b 2 a (S2). Ifthe Device A location data retrieved in S1 is located outside of the 1stzone data retrieved in the previous step, CPU 211 (FIG. 1) of Device Aproceeds to the next step (S3). CPU 211 (FIG. 1) of Device A retrievesthe 1st zone leaving notice data from 1st Zone Leaving Notice DataStorage Area 206A552 b 4 a (S4). CPU 211 (FIG. 1) of Device A outputsthe 1st zone leaving notice data retrieved in the previous step fromSpeaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device A (S5). CPU 211(FIG. 1) of Device A sends the Device B location data transferringrequest to Device B in a wireless fashion (S6). Here, the Device Blocation data transferring request is the request to transfer the DeviceB location data. CPU 211 (FIG. 1) of Device B receives the Device Blocation data transferring request from Device A in a wireless fashion(S7). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B552 b 3 b and sends thedata to Device A in a wireless fashion (S8). CPU 211 (FIG. 1) of DeviceA receives the Device B location data from Device B in a wirelessfashion and stores the data in Device B Location Data Storage Area206A552 b 3 b (S9). CPU 211 (FIG. 1) of Device A retrieves the map datafrom Map Data Storage Area 206A552 b 1 (S10). CPU 211 (FIG. 1) of DeviceA displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device A (S11). CPU 211 (FIG. 1) of Device A retrieves theDevice A location data from Device A Location Data Storage Area 206A552b 3 a (S12). CPU 211 (FIG. 1) of Device A retrieves the Device A iconimage data from Device A Icon Image Data Storage Area 206A552 b 5 a(S13). CPU 211 (FIG. 1) of Device A displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device A retrieves the Device B location datafrom Device B Location Data Storage Area 206A552 b 3 b (S15). CPU 211(FIG. 1) of Device A retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206A552 b 5 b (S16). CPU 211 (FIG. 1) ofDevice A displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Zone Leaving Notice Data OutputtingSoftware 206A552 c 8 of Device A and 2nd Zone Leaving Notice DataOutputting Software 206B552 c 8 of Device B, which output(s) the 2ndzone leaving notice data. In this embodiment, CPU 211 (FIG. 1) of DeviceA retrieves the Device A location data from Device A Location DataStorage Area 206A552 b 3 a (S1). CPU 211 (FIG. 1) of Device A retrievesthe 2nd zone data from 2nd Zone Data Storage Area 206A552 b 2 b (S2). Ifthe Device A location data retrieved in S1 is located outside of the 2ndzone data retrieved in the previous step, CPU 211 (FIG. 1) of Device Aproceeds to the next step (S 3). CPU 211 (FIG. 1) of Device A retrievesthe 2nd zone leaving notice data from 2nd Zone Leaving Notice DataStorage Area 206A552 b 4 b (S4). CPU 211 (FIG. 1) of Device A outputsthe 2nd zone leaving notice data retrieved in the previous step fromSpeaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device A (S5). CPU 211(FIG. 1) of Device A sends the Device B location data transferringrequest to Device B in a wireless fashion (S6). Here, the Device Blocation data transferring request is the request to transfer the DeviceB location data. CPU 211 (FIG. 1) of Device B receives the Device Blocation data transferring request from Device A in a wireless fashion(S7). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B552 b 3 b and sends thedata to Device A in a wireless fashion (S8). CPU 211 (FIG. 1) of DeviceA receives the Device B location data from Device B in a wirelessfashion and stores the data in Device B Location Data Storage Area206A552 b 3 b (S9). CPU 211 (FIG. 1) of Device A retrieves the map datafrom Map Data Storage Area 206A552 b 1 (S10). CPU 211 (FIG. 1) of DeviceA displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device A (S11). CPU 211 (FIG. 1) of Device A retrieves theDevice A location data from Device A Location Data Storage Area 206A552b 3 a (S12). CPU 211 (FIG. 1) of Device A retrieves the Device A iconimage data from Device A Icon Image Data Storage Area 206A552 b 5 a(S13). CPU 211 (FIG. 1) of Device A displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device A retrieves the Device B location datafrom Device B Location Data Storage Area 206A552 b 3 b (S15). CPU 211(FIG. 1) of Device A retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206A552 b 5 b (S16). CPU 211 (FIG. 1) ofDevice A displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 3rd Zone Leaving Notice Data OutputtingSoftware 206A552 c 9 of Device A and 3rd Zone Leaving Notice DataOutputting Software 206B552 c 9 of Device B, which output(s) the 3rdzone leaving notice data. In this embodiment, CPU 211 (FIG. 1) of DeviceA sends the Device B location data transferring request to Device B in awireless fashion (S1). Here, the Device B location data transferringrequest is the request to transfer the Device B location data. CPU 211(FIG. 1) of Device B receives the Device B location data transferringrequest from Device A in a wireless fashion (S2). CPU 211 (FIG. 1) ofDevice B retrieves the Device B location data from Device B LocationData Storage Area 206B552 b 3 b and sends the data to Device A in awireless fashion (S3). CPU 211 (FIG. 1) of Device A receives the DeviceB location data from Device B in a wireless fashion and stores the datain Device B Location Data Storage Area 206A552 b 3 b (S4). CPU 211(FIG. 1) of Device A retrieves the Device B location data from Device BLocation Data Storage Area 206A552 b 3 b (S5). CPU 211 (FIG. 1) ofDevice A retrieves the 3rd zone data from 3rd Zone Data Storage Area206A552 b 2 c (S6). If the Device B location data retrieved in S5 islocated outside of the 3rd zone data retrieved in the previous step, CPU211 (FIG. 1) of Device A proceeds to the next step (S7). CPU 211(FIG. 1) of Device A retrieves the 3rd zone leaving notice data from 3rdZone Leaving Notice Data Storage Area 206A552 b 4 c (S8). CPU 211(FIG. 1) of Device A outputs the 3rd zone leaving notice data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice A (S9). CPU 211 (FIG. 1) of Device A retrieves the map data fromMap Data Storage Area 206A552 b 1 (S10). CPU 211 (FIG. 1) of Device Adisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device A (S11). CPU 211 (FIG. 1) of Device A retrieves the Device Alocation data from Device A Location Data Storage Area 206A552 b 3 a(S12). CPU 211 (FIG. 1) of Device A retrieves the Device A icon imagedata from Device A Icon Image Data Storage Area 206A552 b 5 a (S13). CPU211 (FIG. 1) of Device A displays the Device A icon image data retrievedin the previous step at the location corresponding to the Device Alocation data retrieved in S12 on the map data displayed in S11 (S14).CPU 211 (FIG. 1) of Device A retrieves the Device B location data fromDevice B Location Data Storage Area 206A552 b 3 b (S15). CPU 211(FIG. 1) of Device A retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206A552 b 5 b (S16). CPU 211 (FIG. 1) ofDevice A displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 4th Zone Leaving Notice Data OutputtingSoftware 206A552 c 10 of Device A and 4th Zone Leaving Notice DataOutputting Software 206B552 c 10 of Device B, which output(s) the 4thzone leaving notice data. In this embodiment, CPU 211 (FIG. 1) of DeviceA sends the Device B location data transferring request to Device B in awireless fashion (S1). Here, the Device B location data transferringrequest is the request to transfer the Device B location data. CPU 211(FIG. 1) of Device B receives the Device B location data transferringrequest from Device A in a wireless fashion (S2). CPU 211 (FIG. 1) ofDevice B retrieves the Device B location data from Device B LocationData Storage Area 206B552 b 3 b and sends the data to Device A in awireless fashion (S3). CPU 211 (FIG. 1) of Device A receives the DeviceB location data from Device B in a wireless fashion and stores the datain Device B Location Data Storage Area 206A552 b 3 b (S4). CPU 211(FIG. 1) of Device A retrieves the Device B location data from Device BLocation Data Storage Area 206A552 b 3 b (S5). CPU 211 (FIG. 1) ofDevice A retrieves the 4th zone data from 4th Zone Data Storage Area206A552 b 2 d (S6). If the Device B location data retrieved in S5 islocated outside of the 4th zone data retrieved in the previous step, CPU211 (FIG. 1) of Device A proceeds to the next step (S7). CPU 211(FIG. 1) of Device A retrieves the 4th zone leaving notice data from 4thZone Leaving Notice Data Storage Area 206A552 b 4 d (S8). CPU 211(FIG. 1) of Device A outputs the 4th zone leaving notice data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice A (S9). CPU 211 (FIG. 1) of Device A retrieves the map data fromMap Data Storage Area 206A552 b 1 (S10). CPU 211 (FIG. 1) of Device Adisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device A (S11). CPU 211 (FIG. 1) of Device A retrieves the Device Alocation data from Device A Location Data Storage Area 206A552 b 3 a(S12). CPU 211 (FIG. 1) of Device A retrieves the Device A icon imagedata from Device A Icon Image Data Storage Area 206A552 b 5 a (S13). CPU211 (FIG. 1) of Device A displays the Device A icon image data retrievedin the previous step at the location corresponding to the Device Alocation data retrieved in S12 on the map data displayed in S11 (S14).CPU 211 (FIG. 1) of Device A retrieves the Device B location data fromDevice B Location Data Storage Area 206A552 b 3 b (S15). CPU 211(FIG. 1) of Device A retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206A552 b 5 b (S16). CPU 211 (FIG. 1) ofDevice A displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 1st Zone Leaving Notice Data OutputtingSoftware 206A552 c 7 of Device A and 1st Zone Leaving Notice DataOutputting Software 206B552 c 7 of Device B, which output(s) the 1stzone leaving notice data. In this embodiment, CPU 211 (FIG. 1) of DeviceB sends the Device A location data transferring request to Device A in awireless fashion (S1). Here, the Device A location data transferringrequest is the request to transfer the Device A location data. CPU 211(FIG. 1) of Device A receives the Device A location data transferringrequest from Device B in a wireless fashion (S2). CPU 211 (FIG. 1) ofDevice A retrieves the Device A location data from Device A LocationData Storage Area 206A552 b 3 a and sends the data to Device B in awireless fashion (S3). CPU 211 (FIG. 1) of Device B receives the DeviceA location data from Device A in a wireless fashion and stores the datain Device A Location Data Storage Area 206B552 b 3 a (S4). CPU 211(FIG. 1) of Device B retrieves the Device A location data from Device ALocation Data Storage Area 206B552 b 3 a (S5). CPU 211 (FIG. 1) ofDevice B retrieves the 1st zone data from 1st Zone Data Storage Area206B552 b 2 a (S6). If the Device A location data retrieved in S5 islocated outside of the 1st zone data retrieved in the previous step, CPU211 (FIG. 1) of Device B proceeds to the next step (S7). CPU 211(FIG. 1) of Device B retrieves the 1st zone leaving notice data from 1stZone Leaving Notice Data Storage Area 206B552 b 4 a (S8). CPU 211(FIG. 1) of Device B outputs the 1st zone leaving notice data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice B (S9). CPU 211 (FIG. 1) of Device B retrieves the map data fromMap Data Storage Area 206B552 b 1 (S10). CPU 211 (FIG. 1) of Device Bdisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device B (S11). CPU 211 (FIG. 1) of Device B retrieves the Device Blocation data from Device B Location Data Storage Area 206B552 b 3 b(S12). CPU 211 (FIG. 1) of Device B retrieves the Device B icon imagedata from Device B Icon Image Data Storage Area 206B552 b 5 b (S13). CPU211 (FIG. 1) of Device B displays the Device B icon image data retrievedin the previous step at the location corresponding to the Device Blocation data retrieved in S12 on the map data displayed in S11 (S14).CPU 211 (FIG. 1) of Device B retrieves the Device A location data fromDevice A Location Data Storage Area 206B552 b 3 a (S15). CPU 211(FIG. 1) of Device B retrieves the Device A icon image data from DeviceA Icon Image Data Storage Area 206B552 b 5 a (S16). CPU 211 (FIG. 1) ofDevice B displays the Device A icon image data retrieved in the previousstep at the location corresponding to the Device A location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Zone Leaving Notice Data OutputtingSoftware 206A552 c 8 of Device A and 2nd Zone Leaving Notice DataOutputting Software 206B552 c 8 of Device B, which output(s) the 2ndzone leaving notice data. In this embodiment, CPU 211 (FIG. 1) of DeviceB sends the Device A location data transferring request to Device A in awireless fashion (S1). Here, the Device A location data transferringrequest is the request to transfer the Device A location data. CPU 211(FIG. 1) of Device A receives the Device A location data transferringrequest from Device B in a wireless fashion (S2). CPU 211 (FIG. 1) ofDevice A retrieves the Device A location data from Device A LocationData Storage Area 206A552 b 3 a and sends the data to Device B in awireless fashion (S3). CPU 211 (FIG. 1) of Device B receives the DeviceA location data from Device A in a wireless fashion and stores the datain Device A Location Data Storage Area 206B552 b 3 a (S4). CPU 211(FIG. 1) of Device B retrieves the Device A location data from Device ALocation Data Storage Area 206B552 b 3 a (S5). CPU 211 (FIG. 1) ofDevice B retrieves the 2nd zone data from 2nd Zone Data Storage Area206B552 b 2 b (S6). If the Device A location data retrieved in S5 islocated outside of the 2nd zone data retrieved in the previous step, CPU211 (FIG. 1) of Device B proceeds to the next step (S7). CPU 211(FIG. 1) of Device B retrieves the 2nd zone leaving notice data from 2ndZone Leaving Notice Data Storage Area 206B552 b 4 b (S8). CPU 211(FIG. 1) of Device B outputs the 2nd zone leaving notice data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice B (S9). CPU 211 (FIG. 1) of Device B retrieves the map data fromMap Data Storage Area 206B552 b 1 (S10). CPU 211 (FIG. 1) of Device Bdisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device B (S11). CPU 211 (FIG. 1) of Device B retrieves the Device Blocation data from Device B Location Data Storage Area 206B552 b 3 b(S12). CPU 211 (FIG. 1) of Device B retrieves the Device B icon imagedata from Device B Icon Image Data Storage Area 206B552 b 5 b (S13). CPU211 (FIG. 1) of Device B displays the Device B icon image data retrievedin the previous step at the location corresponding to the Device Blocation data retrieved in S12 on the map data displayed in S11 (S14).CPU 211 (FIG. 1) of Device B retrieves the Device A location data fromDevice A Location Data Storage Area 206B552 b 3 a (S15). CPU 211(FIG. 1) of Device B retrieves the Device A icon image data from DeviceA Icon Image Data Storage Area 206B552 b 5 a (S16). CPU 211 (FIG. 1) ofDevice B displays the Device A icon image data retrieved in the previousstep at the location corresponding to the Device A location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 3rd Zone Leaving Notice Data OutputtingSoftware 206A552 c 9 of Device A and 3rd Zone Leaving Notice DataOutputting Software 206B552 c 9 of Device B, which output(s) the 3rdzone leaving notice data. In this embodiment, CPU 211 (FIG. 1) of DeviceB retrieves the Device B location data from Device B Location DataStorage Area 206B552 b 3 b (S1). CPU 211 (FIG. 1) of Device B retrievesthe 3rd zone data from 3rd Zone Data Storage Area 206B552 b 2 c (S2). Ifthe Device B location data retrieved in 51 is located outside of the 3rdzone data retrieved in the previous step, CPU 211 (FIG. 1) of Device Bproceeds to the next step (S3). CPU 211 (FIG. 1) of Device B retrievesthe 3rd zone leaving notice data from 3rd Zone Leaving Notice DataStorage Area 206B552 b 4 c (S4). CPU 211 (FIG. 1) of Device B outputsthe 3rd zone leaving notice data retrieved in the previous step fromSpeaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B (S5). CPU 211(FIG. 1) of Device B sends the Device A location data transferringrequest to Device A in a wireless fashion (S6). Here, the Device Alocation data transferring request is the request to transfer the DeviceA location data. CPU 211 (FIG. 1) of Device A receives the Device Alocation data transferring request from Device B in a wireless fashion(S7). CPU 211 (FIG. 1) of Device A retrieves the Device A location datafrom Device A Location Data Storage Area 206A552 b 3 a and sends thedata to Device B in a wireless fashion (S8). CPU 211 (FIG. 1) of DeviceB receives the Device A location data from Device A in a wirelessfashion and stores the data in Device A Location Data Storage Area206B552 b 3 a (S9). CPU 211 (FIG. 1) of Device B retrieves the map datafrom Map Data Storage Area 206B552 b 1 (S10). CPU 211 (FIG. 1) of DeviceB displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device B (S11). CPU 211 (FIG. 1) of Device B retrieves theDevice A location data from Device A Location Data Storage Area 206B552b 3 a (S12). CPU 211 (FIG. 1) of Device B retrieves the Device A iconimage data from Device A Icon Image Data Storage Area 206B552 b 5 a(S13). CPU 211 (FIG. 1) of Device B displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B552 b 3 b (S15). CPU 211(FIG. 1) of Device B retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206B552 b 5 b (S16). CPU 211 (FIG. 1) ofDevice B displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 4th Zone Leaving Notice Data OutputtingSoftware 206A552 c 10 of Device A and 4th Zone Leaving Notice DataOutputting Software 206B552 c 10 of Device B, which output(s) the 4thzone leaving notice data. In this embodiment, CPU 211 (FIG. 1) of DeviceB retrieves the Device B location data from Device B Location DataStorage Area 206B552 b 3 b (S1). CPU 211 (FIG. 1) of Device B retrievesthe 4th zone data from 4th Zone Data Storage Area 206B552 b 2 d (S2). Ifthe Device B location data retrieved in S1 is located outside of the 4thzone data retrieved in the previous step, CPU 211 (FIG. 1) of Device Bproceeds to the next step (S3). CPU 211 (FIG. 1) of Device B retrievesthe 4th zone leaving notice data from 4th Zone Leaving Notice DataStorage Area 206B552 b 4 d (S4). CPU 211 (FIG. 1) of Device B outputsthe 4th zone leaving notice data retrieved in the previous step fromSpeaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B (S5). CPU 211(FIG. 1) of Device B sends the Device A location data transferringrequest to Device A in a wireless fashion (S6). Here, the Device Alocation data transferring request is the request to transfer the DeviceA location data. CPU 211 (FIG. 1) of Device A receives the Device Alocation data transferring request from Device B in a wireless fashion(S7). CPU 211 (FIG. 1) of Device A retrieves the Device A location datafrom Device A Location Data Storage Area 206A552 b 3 a and sends thedata to Device B in a wireless fashion (S8). CPU 211 (FIG. 1) of DeviceB receives the Device A location data from Device A in a wirelessfashion and stores the data in Device A Location Data Storage Area206B552 b 3 a (S9). CPU 211 (FIG. 1) of Device B retrieves the map datafrom Map Data Storage Area 206B552 b 1 (S10). CPU 211 (FIG. 1) of DeviceB displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device B (S11). CPU 211 (FIG. 1) of Device B retrieves theDevice A location data from Device A Location Data Storage Area 206B552b 3 a (S12). CPU 211 (FIG. 1) of Device B retrieves the Device A iconimage data from Device A Icon Image Data Storage Area 206B552 b 5 a(S13). CPU 211 (FIG. 1) of Device B displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B552 b 3 b (S15). CPU 211(FIG. 1) of Device B retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206B552 b 5 b (S16). CPU 211 (FIG. 1) ofDevice B displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

<<Zone Entering Notifying Function>>

The following paragraphs illustrate the zone entering notifyingfunction, wherein when Device A enters a specific geographic zoneidentified by Device A, a notice is output from Device A. The notice isfurther output from Device B. In addition, when Device B enters aspecific geographic zone identified by Device A, a notice is output fromDevice A.

This paragraph illustrates the major elements utilized to implement thepresent function. In this embodiment, Host H is connected to Network NT(e.g., the Internet). Device A, a Communication Device 200, is connectedto Network NT (e.g., the Internet) in a wireless fashion. Device B,another Communication Device 200, is connected to Network NT (e.g., theInternet) in a wireless fashion. Host H, Device A, and Device B arecapable to communicate with each other via Network NT (e.g., theInternet) to implement the present function. Device A and Device B arealso capable to communicate with each other directly in a wirelessfashion to implement the present function.

This paragraph illustrates the storage area included in Host H. In thisembodiment, Host H includes Zone Entering Notifying Information StorageArea H553 a of which the data and the software program(s) stored thereinare described hereinafter.

This paragraph illustrates the storage area(s) included in Zone EnteringNotifying Information Storage Area H553 a. In this embodiment, ZoneEntering Notifying Information Storage Area H553 a includes ZoneEntering Notifying Data Storage Area H553 b and Zone Entering NotifyingSoftware Storage Area H553 c. Zone Entering Notifying Data Storage AreaH553 b stores the data necessary to implement the present function onthe side of Host H, such as the one(s) described hereinafter. ZoneEntering Notifying Software Storage Area H553 c stores the softwareprogram(s) necessary to implement the present function on the side ofHost H, such as the one(s) described hereinafter.

This paragraph illustrates the storage area(s) included in Zone EnteringNotifying Data Storage Area H553 b. In this embodiment, Zone EnteringNotifying Data Storage Area H553 b includes Map Data Storage Area H553 b1, Party Zone Data Storage Area H553 b 2, Party Location Data StorageArea H553 b 3, Party Zone Entering Notice Data Storage Area H553 b 4,Party Icon Image Data Storage Area H553 b 5, Party Location NotifyingData Storage Area H553 b 6, and Work Area H553 b 7. Map Data StorageArea H553 b 1 stores the map data which is the image data indicating amap. Party Zone Data Storage Area H553 b 2 stores the data describedhereinafter. Party Location Data Storage Area H553 b 3 stores the datadescribed hereinafter. Party Zone Entering Notice Data Storage Area H553b 4 stores the data described hereinafter. Party Icon Image Data StorageArea H553 b 5 stores the data described hereinafter. Party LocationNotifying Data Storage Area H553 b 6 stores the data describedhereinafter. Work Area H553 b 7 is utilized as a work area to performcalculation and temporarily store data.

This paragraph illustrates the storage area(s) included in Party ZoneData Storage Area H553 b 2. In this embodiment, Party Zone Data StorageArea H553 b 2 includes 1st Zone Data Storage Area H553 b 2 a, 2nd ZoneData Storage Area H553 b 2 b, 3rd Zone Data Storage Area H553 b 2 c, and4th Zone Data Storage Area H553 b 2 d. 1st Zone Data Storage Area H553 b2 a stores the 1st zone data which indicates a certain geographic zoneor area. 2nd Zone Data Storage Area H553 b 2 b stores the 2nd zone datawhich indicates a certain geographic zone or area. 3rd Zone Data StorageArea H553 b 2 c stores the 3rd zone data which indicates a certaingeographic zone or area. 4th Zone Data Storage Area H553 b 2 d storesthe 4th zone data which indicates a certain geographic zone or area.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area H553 b 3. In this embodiment, Party LocationData Storage Area H553 b 3 includes Device A Location Data Storage AreaH553 b 3 a and Device B Location Data Storage Area H553 b 3 b. Device ALocation Data Storage Area H553 b 3 a stores the Device A location datawhich indicates the current geographic location of Device A in (x,y,z)format. Device B Location Data Storage Area H553 b 3 b stores the DeviceB location data which indicates the current geographic location ofDevice B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in Party ZoneEntering Notice Data Storage Area H553 b 4. In this embodiment, PartyZone Entering Notice Data Storage Area H553 b 4 includes 1st ZoneEntering Notice Data Storage Area H553 b 4 a, 2nd Zone Entering NoticeData Storage Area H553 b 4 b, 3rd Zone Entering Notice Data Storage AreaH553 b 4 c, and 4th Zone Entering Notice Data Storage Area H553 b 4 d.1st Zone Entering Notice Data Storage Area H553 b 4 a stores the 1stzone entering notice data which is the audiovisual data indicating thatDevice A entered the zone indicated by the 1st zone data. 2nd ZoneEntering Notice Data Storage Area H553 b 4 b stores the 2nd zoneentering notice data which is the audiovisual data indicating thatDevice A entered the zone indicated by the 2nd zone data. 3rd ZoneEntering Notice Data Storage Area H553 b 4 c stores the 3rd zoneentering notice data which is the audiovisual data indicating thatDevice B entered the zone indicated by the 3rd zone data. 4th ZoneEntering Notice Data Storage Area H553 b 4 d stores the 4th zoneentering notice data which is the audiovisual data indicating thatDevice B entered the zone indicated by the 4th zone data.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area H553 b 5. In this embodiment, Party Icon ImageData Storage Area H553 b 5 includes Device A Icon Image Data StorageArea H553 b 5 a and Device B Icon Image Data Storage Area H553 b 5 b.Device A Icon Image Data Storage Area H553 b 5 a stores the Device Aicon image data which is the image data of the icon indicating thecurrent geographic location of Device A on the map data. Device B IconImage Data Storage Area H553 b 5 b stores the Device B icon image datawhich is the image data of the icon indicating the current geographiclocation of Device B on the map data.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area H553 b 6. In this embodiment, PartyLocation Notifying Data Storage Area H553 b 6 includes Device A LocationNotifying Data Storage Area H553 b 6 a and Device B Location NotifyingData Storage Area H553 b 6 b. Device A Location Notifying Data StorageArea H553 b 6 a stores the Device A location notifying data which is theaudiovisual data notifying that the current geographic location ofDevice A is notified. Device B Location Notifying Data Storage Area H553b 6 b stores the Device B location notifying data which is theaudiovisual data notifying that the current geographic location ofDevice B is notified.

This paragraph illustrates the software program(s) stored in ZoneEntering Notifying Software Storage Area H553 c. In this embodiment,Zone Entering Notifying Software Storage Area H553 c stores 1st ZoneData Producing Software H553 c 1, 2nd Zone Data Producing Software H553c 2, 3rd Zone Data Producing Software H553 c 3, 4th Zone Data ProducingSoftware H553 c 4, Device A Location Data Producing Software H553 c 5,1st Zone Entering Notice Data Outputting Software H553 c 7, 2nd ZoneEntering Notice Data Outputting Software H553 c 8, 3rd Zone EnteringNotice Data Outputting Software H553 c 9, and 4th Zone Entering NoticeData Outputting Software H553 c 10. 1st Zone Data Producing SoftwareH553 c 1 is the software program described hereinafter. 2nd Zone DataProducing Software H553 c 2 is the software program describedhereinafter. 3rd Zone Data Producing Software H553 c 3 is the softwareprogram described hereinafter. 4th Zone Data Producing Software H553 c 4is the software program described hereinafter. Device A Location DataProducing Software H553 c 5 is the software program describedhereinafter. 1st Zone Entering Notice Data Outputting Software H553 c 7is the software program described hereinafter. 2nd Zone Entering NoticeData Outputting Software H553 c 8 is the software program describedhereinafter. 3rd Zone Entering Notice Data Outputting Software H553 c 9is the software program described hereinafter. 4th Zone Entering NoticeData Outputting Software H553 c 10 is the software program describedhereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device A. In this embodiment, RAM 206 includes Zone EnteringNotifying Information Storage Area 206A553 a of which the data and thesoftware program(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device A.

This paragraph illustrates the storage area(s) included in Zone EnteringNotifying Information Storage Area 206A553 a. In this embodiment, ZoneEntering Notifying Information Storage Area 206A553 a includes ZoneEntering Notifying Data Storage Area 206A553 b and Zone EnteringNotifying Software Storage Area 206A553 c. Zone Entering Notifying DataStorage Area 206A553 b stores the data necessary to implement thepresent function on the side of Device A, such as the one(s) describedhereinafter. Zone Entering Notifying Software Storage Area 206A553 cstores the software program(s) necessary to implement the presentfunction on the side of Device A, such as the one(s) describedhereinafter.

This paragraph illustrates the storage area(s) included in Zone EnteringNotifying Data Storage Area 206A553 b. In this embodiment, Zone EnteringNotifying Data Storage Area 206A553 b includes Map Data Storage Area206A553 b 1, Party Zone Data Storage Area 206A553 b 2, Party LocationData Storage Area 206A553 b 3, Party Zone Entering Notice Data StorageArea 206A553 b 4, Party Icon Image Data Storage Area 206A553 b 5, PartyLocation Notifying Data Storage Area 206A553 b 6, and Work Area 206A553b 7. Map Data Storage Area 206A553 b 1 stores the map data which is theimage data indicating a map. Party Zone Data Storage Area 206A553 b 2stores the data described hereinafter. Party Location Data Storage Area206A553 b 3 stores the data described hereinafter. Party Zone EnteringNotice Data Storage Area 206A553 b 4 stores the data describedhereinafter. Party Icon Image Data Storage Area 206A553 b 5 stores thedata described hereinafter. Party Location Notifying Data Storage Area206A553 b 6 stores the data described hereinafter. Work Area 206A553 b 7is utilized as a work area to perform calculation and temporarily storedata.

This paragraph illustrates the storage area(s) included in Party ZoneData Storage Area 206A553 b 2. In this embodiment, Party Zone DataStorage Area 206A553 b 2 includes 1st Zone Data Storage Area 206A553 b 2a, 2nd Zone Data Storage Area 206A553 b 2 b, 3rd Zone Data Storage Area206A553 b 2 c, and 4th Zone Data Storage Area 206A553 b 2 d. 1st ZoneData Storage Area 206A553 b 2 a stores the 1st zone data which indicatesa certain geographic zone or area. 2nd Zone Data Storage Area 206A553 b2 b stores the 2nd zone data which indicates a certain geographic zoneor area. 3rd Zone Data Storage Area 206A553 b 2 c stores the 3rd zonedata which indicates a certain geographic zone or area. 4th Zone DataStorage Area 206A553 b 2 d stores the 4th zone data which indicates acertain geographic zone or area.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area 206A553 b 3. In this embodiment, PartyLocation Data Storage Area 206A553 b 3 includes Device A Location DataStorage Area 206A553 b 3 a and Device B Location Data Storage Area206A553 b 3 b. Device A Location Data Storage Area 206A553 b 3 a storesthe Device A location data which indicates the current geographiclocation of Device A in (x,y,z) format. Device B Location Data StorageArea 206A553 b 3 b stores the Device B location data which indicates thecurrent geographic location of Device B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in Party ZoneEntering Notice Data Storage Area 206A553 b 4. In this embodiment, PartyZone Entering Notice Data Storage Area 206A553 b 4 includes 1st ZoneEntering Notice Data Storage Area 206A553 b 4 a, 2nd Zone EnteringNotice Data Storage Area 206A553 b 4 b, 3rd Zone Entering Notice DataStorage Area 206A553 b 4 c, and 4th Zone Entering Notice Data StorageArea 206A553 b 4 d. 1st Zone Entering Notice Data Storage Area 206A553 b4 a stores the 1st zone entering notice data which is the audiovisualdata indicating that Device A entered the zone indicated by the 1st zonedata. 2nd Zone Entering Notice Data Storage Area 206A553 b 4 b storesthe 2nd zone entering notice data which is the audiovisual dataindicating that Device A entered the zone indicated by the 2nd zonedata. 3rd Zone Entering Notice Data Storage Area 206A553 b 4 c storesthe 3rd zone entering notice data which is the audiovisual dataindicating that Device B entered the zone indicated by the 3rd zonedata. 4th Zone Entering Notice Data Storage Area 206A553 b 4 d storesthe 4th zone entering notice data which is the audiovisual dataindicating that Device B entered the zone indicated by the 4th zonedata.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area 206A553 b 5. In this embodiment, Party IconImage Data Storage Area 206A553 b 5 includes Device A Icon Image DataStorage Area 206A553 b 5 a and Device B Icon Image Data Storage Area206A553 b 5 b. Device A Icon Image Data Storage Area 206A553 b 5 astores the Device A icon image data which is the image data of the iconindicating the current geographic location of Device A on the map data.Device B Icon Image Data Storage Area 206A553 b 5 b stores the Device Bicon image data which is the image data of the icon indicating thecurrent geographic location of Device B on the map data.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area 206A553 b 6. In this embodiment,Party Location Notifying Data Storage Area 206A553 b 6 includes Device ALocation Notifying Data Storage Area 206A553 b 6 a and Device B LocationNotifying Data Storage Area 206A553 b 6 b. Device A Location NotifyingData Storage Area 206A553 b 6 a stores the Device A location notifyingdata which is the audiovisual data notifying that the current geographiclocation of Device A is notified. Device B Location Notifying DataStorage Area 206A553 b 6 b stores the Device B location notifying datawhich is the audiovisual data notifying that the current geographiclocation of Device B is notified.

This paragraph illustrates the software program(s) stored in ZoneEntering Notifying Software Storage Area 206A553 c. In this embodiment,Zone Entering Notifying Software Storage Area 206A553 c stores 1st ZoneData Producing Software 206A553 c 1, 2nd Zone Data Producing Software206A553 c 2, 3rd Zone Data Producing Software 206A553 c 3, 4th Zone DataProducing Software 206A553 c 4, Device A Location Data ProducingSoftware 206A553 c 5, 1st Zone Entering Notice Data Outputting Software206A553 c 7, 2nd Zone Entering Notice Data Outputting Software 206A553 c8, 3rd Zone Entering Notice Data Outputting Software 206A553 c 9, and4th Zone Entering Notice Data Outputting Software 206A553 c 10. 1st ZoneData Producing Software 206A553 c 1 is the software program describedhereinafter. 2nd Zone Data Producing Software 206A553 c 2 is thesoftware program described hereinafter. 3rd Zone Data Producing Software206A553 c 3 is the software program described hereinafter. 4th Zone DataProducing Software 206A553 c 4 is the software program describedhereinafter. Device A Location Data Producing Software 206A553 c 5 isthe software program described hereinafter. 1st Zone Entering NoticeData Outputting Software 206A553 c 7 is the software program describedhereinafter. 2nd Zone Entering Notice Data Outputting Software 206A553 c8 is the software program described hereinafter. 3rd Zone EnteringNotice Data Outputting Software 206A553 c 9 is the software programdescribed hereinafter. 4th Zone Entering Notice Data Outputting Software206A553 c 10 is the software program described hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device B. In this embodiment, RAM 206 includes Zone EnteringNotifying Information Storage Area 206B553 a of which the data and thesoftware program(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device B.

This paragraph illustrates the storage area(s) included in Zone EnteringNotifying Information Storage Area 206B553 a. In this embodiment, ZoneEntering Notifying Information Storage Area 206B553 a includes ZoneEntering Notifying Data Storage Area 206B553 b and Zone EnteringNotifying Software Storage Area 206B553 c. Zone Entering Notifying DataStorage Area 206B553 b stores the data necessary to implement thepresent function on the side of Device B, such as the one(s) describedhereinafter. Zone Entering Notifying Software Storage Area 206B553 cstores the software program(s) necessary to implement the presentfunction on the side of Device B, such as the one(s) describedhereinafter.

This paragraph illustrates the storage area(s) included in Zone EnteringNotifying Data Storage Area 206B553 b. In this embodiment, Zone EnteringNotifying Data Storage Area 206B553 b includes Map Data Storage Area206B553 b 1, Party Zone Data Storage Area 206B553 b 2, Party LocationData Storage Area 206B553 b 3, Party Zone Entering Notice Data StorageArea 206B553 b 4, Party Icon Image Data Storage Area 206B553 b 5, PartyLocation Notifying Data Storage Area 206B553 b 6, and Work Area 206B553b 7. Map Data Storage Area 206B553 b 1 stores the map data which is theimage data indicating a map. Party Zone Data Storage Area 206B553 b 2stores the data described hereinafter. Party Location Data Storage Area206B553 b 3 stores the data described hereinafter. Party Zone EnteringNotice Data Storage Area 206B553 b 4 stores the data describedhereinafter. Party Icon Image Data Storage Area 206B553 b 5 stores thedata described hereinafter. Party Location Notifying Data Storage Area206B553 b 6 stores the data described hereinafter. Work Area 206B553 b 7is utilized as a work area to perform calculation and temporarily storedata.

This paragraph illustrates the storage area(s) included in Party ZoneData Storage Area 206B553 b 2. In this embodiment, Party Zone DataStorage Area 206B553 b 2 includes 1st Zone Data Storage Area 206B553 b 2a, 2nd Zone Data Storage Area 206B553 b 2 b, 3rd Zone Data Storage Area206B553 b 2 c, and 4th Zone Data Storage Area 206B553 b 2 d. 1st ZoneData Storage Area 206B553 b 2 a stores the 1st zone data which indicatesa certain geographic zone or area. 2nd Zone Data Storage Area 206B553 b2 b stores the 2nd zone data which indicates a certain geographic zoneor area. 3rd Zone Data Storage Area 206B553 b 2 c stores the 3rd zonedata which indicates a certain geographic zone or area. 4th Zone DataStorage Area 206B553 b 2 d stores the 4th zone data which indicates acertain geographic zone or area.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area 206B553 b 3. In this embodiment, PartyLocation Data Storage Area 206B553 b 3 includes Device A Location DataStorage Area 206B553 b 3 a and Device B Location Data Storage Area206B553 b 3 b. Device A Location Data Storage Area 206B553 b 3 a storesthe Device A location data which indicates the current geographiclocation of Device A in (x,y,z) format. Device B Location Data StorageArea 206B553 b 3 b stores the Device B location data which indicates thecurrent geographic location of Device B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in Party ZoneEntering Notice Data Storage Area 206B553 b 4. In this embodiment, PartyZone Entering Notice Data Storage Area 206B553 b 4 includes 1st ZoneEntering Notice Data Storage Area 206B553 b 4 a, 2nd Zone EnteringNotice Data Storage Area 206B553 b 4 b, 3rd Zone Entering Notice DataStorage Area 206B553 b 4 c, and 4th Zone Entering Notice Data StorageArea 206B553 b 4 d. 1st Zone Entering Notice Data Storage Area 206B553 b4 a stores the 1st zone entering notice data which is the audiovisualdata indicating that Device A entered the zone indicated by the 1st zonedata. 2nd Zone Entering Notice Data Storage Area 206B553 b 4 b storesthe 2nd zone entering notice data which is the audiovisual dataindicating that Device A entered the zone indicated by the 2nd zonedata. 3rd Zone Entering Notice Data Storage Area 206B553 b 4 c storesthe 3rd zone entering notice data which is the audiovisual dataindicating that Device B entered the zone indicated by the 3rd zonedata. 4th Zone Entering Notice Data Storage Area 206B553 b 4 d storesthe 4th zone entering notice data which is the audiovisual dataindicating that Device B entered the zone indicated by the 4th zonedata.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area 206B553 b 5. In this embodiment, Party IconImage Data Storage Area 206B553 b 5 includes Device A Icon Image DataStorage Area 206B553 b 5 a and Device B Icon Image Data Storage Area206B553 b 5 b. Device A Icon Image Data Storage Area 206B553 b 5 astores the Device A icon image data which is the image data of the iconindicating the current geographic location of Device A on the map data.Device B Icon Image Data Storage Area 206B553 b 5 b stores the Device Bicon image data which is the image data of the icon indicating thecurrent geographic location of Device B on the map data.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area 206B553 b 6. In this embodiment,Party Location Notifying Data Storage Area 206B553 b 6 includes Device ALocation Notifying Data Storage Area 206B553 b 6 a and Device B LocationNotifying Data Storage Area 206B553 b 6 b. Device A Location NotifyingData Storage Area 206B553 b 6 a stores the Device A location notifyingdata which is the audiovisual data notifying that the current geographiclocation of Device A is notified. Device B Location Notifying DataStorage Area 206B553 b 6 b stores the Device B location notifying datawhich is the audiovisual data notifying that the current geographiclocation of Device B is notified.

This paragraph illustrates the software program(s) stored in ZoneEntering Notifying Software Storage Area 206B553 c. In this embodiment,Zone Entering Notifying Software Storage Area 206B553 c stores 1st ZoneData Producing Software 206B553 c 1, 2nd Zone Data Producing Software206B553 c 2, 3rd Zone Data Producing Software 206B553 c 3, 4th Zone DataProducing Software 206B553 c 4, Device B Location Data ProducingSoftware 206B553 c 6, 1st Zone Entering Notice Data Outputting Software206B553 c 7, 2nd Zone Entering Notice Data Outputting Software 206B553 c8, 3rd Zone Entering Notice Data Outputting Software 206B553 c 9, and4th Zone Entering Notice Data Outputting Software 206B553 c 10. 1st ZoneData Producing Software 206B553 c 1 is the software program describedhereinafter. 2nd Zone Data Producing Software 206B553 c 2 is thesoftware program described hereinafter. 3rd Zone Data Producing Software206B553 c 3 is the software program described hereinafter. 4th Zone DataProducing Software 206B553 c 4 is the software program describedhereinafter. Device B Location Data Producing Software 206B553 c 6 isthe software program described hereinafter. 1st Zone Entering NoticeData Outputting Software 206B553 c 7 is the software program describedhereinafter. 2nd Zone Entering Notice Data Outputting Software 206B553 c8 is the software program described hereinafter. 3rd Zone EnteringNotice Data Outputting Software 206B553 c 9 is the software programdescribed hereinafter. 4th Zone Entering Notice Data Outputting Software206B553 c 10 is the software program described hereinafter.

This paragraph illustrate(s) 1st Zone Data Producing Software H553 c 1of Host H and 1st Zone Data Producing Software 206A553 c 1 of Device A,which produce(s) the 1st zone data. In this embodiment, Host H retrievesthe map data from Map Data Storage Area H553 b 1 and sends the data toDevice A (S1). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S2). The user of Device A selects, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, a specific zone onthe map data displayed in the previous step (S3). CPU 211 (FIG. 1) ofDevice A produces the 1st zone data by referring to the specific zoneselected in the previous step and sends the data to Host H in a wirelessfashion (S4). Host H receives the 1st zone data from Device A and storesthe data in 1st Zone Data Storage Area H553 b 2 a (S5).

This paragraph illustrate(s) 2nd Zone Data Producing Software H553 c 2of Host H and 2nd Zone Data Producing Software 206A553 c 2 of Device A,which produce(s) the 2nd zone data. In this embodiment, Host H retrievesthe map data from Map Data Storage Area H553 b 1 and sends the data toDevice A (S1). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S2). The user of Device A selects, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, a specific zone onthe map data displayed in the previous step (S3). CPU 211 (FIG. 1) ofDevice A produces the 2nd zone data by referring to the specific zoneselected in the previous step and sends the data to Host H in a wirelessfashion (S4). Host H receives the 2nd zone data from Device A and storesthe data in 2nd Zone Data Storage Area H553 b 2 b (S5).

This paragraph illustrate(s) 3rd Zone Data Producing Software H553 c 3of Host H and 3rd Zone Data Producing Software 206A553 c 3 of Device A,which produce(s) the 3rd zone data. In this embodiment, Host H retrievesthe map data from Map Data Storage Area H553 b 1 and sends the data toDevice A (S1). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S2). The user of Device A selects, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, a specific zone onthe map data displayed in the previous step (S3). CPU 211 (FIG. 1) ofDevice A produces the 3rd zone data by referring to the specific zoneselected in the previous step and sends the data to Host H in a wirelessfashion (S4). Host H receives the 3rd zone data from Device A and storesthe data in 3rd Zone Data Storage Area H553 b 2 c (S5).

This paragraph illustrate(s) 4th Zone Data Producing Software H553 c 4of Host H and 4th Zone Data Producing Software 206A553 c 4 of Device A,which produce(s) the 4th zone data. In this embodiment, Host H retrievesthe map data from Map Data Storage Area H553 b 1 and sends the data toDevice A (S1). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S2). The user of Device A selects, by utilizing InputDevice 210 (FIG. 1) or via voice recognition system, a specific zone onthe map data displayed in the previous step (S3). CPU 211 (FIG. 1) ofDevice A produces the 4th zone data by referring to the specific zoneselected in the previous step and sends the data to Host H in a wirelessfashion (S4). Host H receives the 4th zone data from Device A and storesthe data in 4th Zone Data Storage Area H553 b 2 d (S5).

This paragraph illustrate(s) 1st Zone Data Producing Software 206B553 c1 of Device B, which produces) the 1st zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B553 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 1st zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 1st zonedata produced in the previous step in 1st Zone Data Storage Area 206B553b 2 a (S5).

This paragraph illustrate(s) 2nd Zone Data Producing Software 206B553 c2 of Device B, which produce(s) the 2nd zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B553 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 2nd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 2nd zonedata produced in the previous step in 2nd Zone Data Storage Area 206B553b 2 b (S5).

This paragraph illustrate(s) 3rd Zone Data Producing Software 206B553 c3 of Device B, which produce(s) the 3rd zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B553 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 3rd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 3rd zonedata produced in the previous step in 3rd Zone Data Storage Area 206B553b 2 c (S5).

This paragraph illustrate(s) 4th Zone Data Producing Software 206B553 c4 of Device B, which produce(s) the 4th zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B553 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 4th zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 4th zonedata produced in the previous step in 4th Zone Data Storage Area 206B553b 2 d (S5).

This paragraph illustrate(s) Device A Location Data Producing SoftwareH553 c 5 of Host H and Device A Location Data Producing Software 206A553c 5 of Device A, which produces) Device A location data. In thisembodiment, CPU 211 (FIG. 1) of Device A identifies the current locationof Device A (S1). CPU 211 (FIG. 1) of Device A produces the Device Alocation data by utilizing the current location identified in theprevious step and sends the data to Host H in a wireless fashion (S2).Host H receives the Device A location data from Device A and stores thedata in Device A Location Data Storage Area H553 b 3 a (S3). Theforegoing sequence is repeated periodically.

This paragraph illustrate(s) Device B Location Data Producing Software206B553 c 6 of Device B, which produce(s) Device B location data. Inthis embodiment, CPU 211 (FIG. 1) of Device B identifies the currentlocation of Device B (S1). CPU 211 (FIG. 1) of Device B produces theDevice B location data by utilizing the current location identified inthe previous step (S2). CPU 211 (FIG. 1) of Device B stores the Device Blocation data produced in the previous step in Device B Location DataStorage Area 206B553 b 3 b (S3). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 1st Zone Entering Notice Data OutputtingSoftware H553 c 7 of Host H, 1st Zone Entering Notice Data OutputtingSoftware 206A553 c 7 of Device A, and 1st Zone Entering Notice DataOutputting Software 206B553 c 7 of Device B, which output(s) the 1stzone entering notice data. In this embodiment, Host H retrieves theDevice A location data from Device A Location Data Storage Area H553 b 3a (S1). Host H retrieves the 1st zone data from 1st Zone Data StorageArea H553 b 2 a (S2). If the Device A location data retrieved in S1 islocated inside of the 1st zone data retrieved in the previous step, HostH proceeds to the next step (S3). Host H retrieves the 1st zone enteringnotice data from 1st Zone Entering Notice Data Storage Area H553 b 4 aand sends the data to Device A (S4). CPU 211 (FIG. 1) of Device Areceives the 1st zone entering notice data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S5). Host H sends the Device B location datatransferring request to Device B (S6). Here, the Device B location datatransferring request is the request to transfer the Device B locationdata. CPU 211 (FIG. 1) of Device B receives the Device B location datatransferring request from Host H in a wireless fashion (S7). CPU 211(FIG. 1) of Device B retrieves the Device B location data from Device BLocation Data Storage Area 206B553 b 3 b and sends the data to Host H ina wireless fashion (S8). Host H receives the Device B location data fromDevice B and stores the data in Device B Location Data Storage Area H553b 3 b (S9). Host H retrieves the map data from Map Data Storage AreaH553 b 1 and sends the data to Device A (S10). CPU 211 (FIG. 1) ofDevice A receives the map data from Host H in a wireless fashion anddisplays the data on LCD 201 (FIG. 1) of Device A (S11). Host Hretrieves the Device A location data from Device A Location Data StorageArea H553 b 3 a and sends the data to Device A (S12). CPU 211 (FIG. 1)of Device A receives the Device A location data from Host H in awireless fashion (S13). Host H retrieves the Device A icon image datafrom Device A Icon Image Data Storage Area H553 b 5 a and sends the datato Device A (S14). CPU 211 (FIG. 1) of Device A receives the Device Aicon image data from Host H in a wireless fashion (S15). CPU 211(FIG. 1) of Device A displays the Device A icon image data received inthe previous step at the location corresponding to the Device A locationdata received in S13 on the map data displayed in S11 (S16). Host Hretrieves the Device B location data from Device B Location Data StorageArea H553 b 3 b and sends the data to Device A (S17). CPU 211 (FIG. 1)of Device A receives the Device B location data from Host H in awireless fashion (S18). Host H retrieves the Device B icon image datafrom Device B Icon Image Data Storage Area H553 b 5 b and sends the datato Device A (S19). CPU 211 (FIG. 1) of Device A receives the Device Bicon image data from Host H in a wireless fashion (S20). CPU 211(FIG. 1) of Device A displays the Device B icon image data received inthe previous step at the location corresponding to the Device B locationdata received in S18 on the map data displayed in S11 (S21). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Zone Entering Notice Data OutputtingSoftware H553 c 8 of Host H, 2nd Zone Entering Notice Data OutputtingSoftware 206A553 c 8 of Device A, and 2nd Zone Entering Notice DataOutputting Software 206B553 c 8 of Device B, which output(s) the 2ndzone entering notice data. In this embodiment, Host H retrieves theDevice A location data from Device A Location Data Storage Area H553 b 3a (S1). Host H retrieves the 2nd zone data from 2nd Zone Data StorageArea H553 b 2 b (S2). If the Device A location data retrieved in S1 islocated inside of the 2nd zone data retrieved in the previous step, HostH proceeds to the next step (S3). Host H retrieves the 2nd zone enteringnotice data from 2nd Zone Entering Notice Data Storage Area H553 b 4 band sends the data to Device A (S4). CPU 211 (FIG. 1) of Device Areceives the 2nd zone entering notice data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S5). Host H sends the Device B location datatransferring request to Device B (S6). Here, the Device B location datatransferring request is the request to transfer the Device B locationdata. CPU 211 (FIG. 1) of Device B receives the Device B location datatransferring request from Host H in a wireless fashion (S7). CPU 211(FIG. 1) of Device B retrieves the Device B location data from Device BLocation Data Storage Area 206B553 b 3 b and sends the data to Host H ina wireless fashion (S8). Host H receives the Device B location data fromDevice B and stores the data in Device B Location Data Storage Area H553b 3 b (S9). Host H retrieves the map data from Map Data Storage AreaH553 b 1 and sends the data to Device A (S10). CPU 211 (FIG. 1) ofDevice A receives the map data from Host H in a wireless fashion anddisplays the data on LCD 201 (FIG. 1) of Device A (S11). Host Hretrieves the Device A location data from Device A Location Data StorageArea H553 b 3 a and sends the data to Device A (S12). CPU 211 (FIG. 1)of Device A receives the Device A location data from Host H in awireless fashion (S13). Host H retrieves the Device A icon image datafrom Device A Icon Image Data Storage Area H553 b 5 a and sends the datato Device A (S14). CPU 211 (FIG. 1) of Device A receives the Device Aicon image data from Host H in a wireless fashion (S15). CPU 211(FIG. 1) of Device A displays the Device A icon image data received inthe previous step at the location corresponding to the Device A locationdata received in S13 on the map data displayed in S11 (S16). Host Hretrieves the Device B location data from Device B Location Data StorageArea H553 b 3 b and sends the data to Device A (S17). CPU 211 (FIG. 1)of Device A receives the Device B location data from Host H in awireless fashion (S18). Host H retrieves the Device B icon image datafrom Device B Icon Image Data Storage Area H553 b 5 b and sends the datato Device A (S19). CPU 211 (FIG. 1) of Device A receives the Device Bicon image data from Host H in a wireless fashion (S20). CPU 211(FIG. 1) of Device A displays the Device B icon image data received inthe previous step at the location corresponding to the Device B locationdata received in S18 on the map data displayed in S11 (S21). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 3rd Zone Entering Notice Data OutputtingSoftware H553 c 9 of Host H, 3rd Zone Entering Notice Data OutputtingSoftware 206A553 c 9 of Device A, and 3rd Zone Entering Notice DataOutputting Software 206B553 c 9 of Device B, which output(s) the 3rdzone entering notice data. In this embodiment, Host H sends the Device Blocation data transferring request to Device B (S1). Here, the Device Blocation data transferring request is the request to transfer the DeviceB location data. CPU 211 (FIG. 1) of Device B receives the Device Blocation data transferring request from Host H in a wireless fashion(S2). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B553 b 3 b and sends thedata to Host H in a wireless fashion (S3). Host H receives the Device Blocation data from Device B and stores the data in Device B LocationData Storage Area H553 b 3 b (S4). Host H retrieves the Device Blocation data from Device B Location Data Storage Area H553 b 3 b (S5).Host H retrieves the 3rd zone data from 3rd Zone Data Storage Area H553b 2 c (S6). If the Device B location data retrieved in S5 is locatedinside of the 3rd zone data retrieved in the previous step, Host Hproceeds to the next step (S7). Host H retrieves the 3rd zone enteringnotice data from 3rd Zone Entering Notice Data Storage Area H553 b 4 cand sends the data to Device A (S8). CPU 211 (FIG. 1) of Device Areceives the 3rd zone entering notice data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S9). Host H retrieves the map data from Map DataStorage Area H553 b 1 and sends the data to Device A (S10). CPU 211(FIG. 1) of Device A receives the map data from Host H in a wirelessfashion and displays the data on LCD 201 (FIG. 1) of Device A (S11).Host H retrieves the Device A location data from Device A Location DataStorage Area H553 b 3 a and sends the data to Device A (S12). CPU 211(FIG. 1) of Device A receives the Device A location data from Host H ina wireless fashion (S13). Host H retrieves the Device A icon image datafrom Device A Icon Image Data Storage Area H553 b 5 a and sends the datato Device A (S14). CPU 211 (FIG. 1) of Device A receives the Device Aicon image data from Host H in a wireless fashion (S15). CPU 211(FIG. 1) of Device A displays the Device A icon image data received inthe previous step at the location corresponding to the Device A locationdata received in S13 on the map data displayed in S11 (S16). Host Hretrieves the Device B location data from Device B Location Data StorageArea H553 b 3 b and sends the data to Device A (S17). CPU 211 (FIG. 1)of Device A receives the Device B location data from Host H in awireless fashion (S18). Host H retrieves the Device B icon image datafrom Device B Icon Image Data Storage Area H553 b 5 b and sends the datato Device A (S19). CPU 211 (FIG. 1) of Device A receives the Device Bicon image data from Host H in a wireless fashion (S20). CPU 211(FIG. 1) of Device A displays the Device B icon image data received inthe previous step at the location corresponding to the Device B locationdata received in S18 on the map data displayed in S11 (S21). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 4th Zone Entering Notice Data OutputtingSoftware H553 c 10 of Host H, 4th Zone Entering Notice Data OutputtingSoftware 206A553 c 10 of Device A, and 4th Zone Entering Notice DataOutputting Software 206B553 c 10 of Device B, which output(s) the 4thzone entering notice data. In this embodiment, Host H sends the Device Blocation data transferring request to Device B (S1). Here, the Device Blocation data transferring request is the request to transfer the DeviceB location data. CPU 211 (FIG. 1) of Device B receives the Device Blocation data transferring request from Host H in a wireless fashion(S2). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B553 b 3 b and sends thedata to Host H in a wireless fashion (S3). Host H receives the Device Blocation data from Device B and stores the data in Device B LocationData Storage Area H553 b 3 b (S4). Host H retrieves the Device Blocation data from Device B Location Data Storage Area H553 b 3 b (S5).Host H retrieves the 4th zone data from 4th Zone Data Storage Area H553b 2 d (S6). If the Device B location data retrieved in S5 is locatedinside of the 4th zone data retrieved in the previous step, Host Hproceeds to the next step (S7). Host H retrieves the 4th zone enteringnotice data from 4th Zone Entering Notice Data Storage Area H553 b 4 dand sends the data to Device A (S8). CPU 211 (FIG. 1) of Device Areceives the 4th zone entering notice data from Host H in a wirelessfashion and outputs the data from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S9). Host H retrieves the map data from Map DataStorage Area H553 b 1 and sends the data to Device A (S10). CPU 211(FIG. 1) of Device A receives the map data from Host H in a wirelessfashion and displays the data on LCD 201 (FIG. 1) of Device A (S11).Host H retrieves the Device A location data from Device A Location DataStorage Area H553 b 3 a and sends the data to Device A (S12). CPU 211(FIG. 1) of Device A receives the Device A location data from Host H ina wireless fashion (S13). Host H retrieves the Device A icon image datafrom Device A Icon Image Data Storage Area H553 b 5 a and sends the datato Device A (S14). CPU 211 (FIG. 1) of Device A receives the Device Aicon image data from Host H in a wireless fashion (S15). CPU 211(FIG. 1) of Device A displays the Device A icon image data received inthe previous step at the location corresponding to the Device A locationdata received in S13 on the map data displayed in S11 (S16). Host Hretrieves the Device B location data from Device B Location Data StorageArea H553 b 3 b and sends the data to Device A (S17). CPU 211 (FIG. 1)of Device A receives the Device B location data from Host H in awireless fashion (S18). Host H retrieves the Device B icon image datafrom Device B Icon Image Data Storage Area H553 b 5 b and sends the datato Device A (S19). CPU 211 (FIG. 1) of Device A receives the Device Bicon image data from Host H in a wireless fashion (S20). CPU 211(FIG. 1) of Device A displays the Device B icon image data received inthe previous step at the location corresponding to the Device B locationdata received in S18 on the map data displayed in S11 (S21). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 1st Zone Entering Notice Data OutputtingSoftware H553 c 7 of Host H and 1st Zone Entering Notice Data OutputtingSoftware 206B553 c 7 of Device B, which output(s) the 1st zone enteringnotice data. In this embodiment, CPU 211 (FIG. 1) of Device B sends theDevice A location data transferring request to Host H in a wirelessfashion (S1). Here, the Device A location data transferring request isthe request to transfer the Device A location data. Host H receives theDevice A location data transferring request from Device B (S2). Host Hretrieves the Device A location data from Device A Location Data StorageArea H553 b 3 a and sends the data to Device B (S3). CPU 211 (FIG. 1) ofDevice B receives the Device A location data from Host H in a wirelessfashion and stores the data in Device A Location Data Storage Area206B553 b 3 a (S4). CPU 211 (FIG. 1) of Device B retrieves the Device Alocation data from Device A Location Data Storage Area 206B553 b 3 a(S5). CPU 211 (FIG. 1) of Device B retrieves the 1st zone data from 1stZone Data Storage Area 206B553 b 2 a (S6). If the Device A location dataretrieved in S5 is located inside of the 1st zone data retrieved in theprevious step, CPU 211 (FIG. 1) of Device B proceeds to the next step(S7). CPU 211 (FIG. 1) of Device B retrieves the 1st zone enteringnotice data from 1st Zone Entering Notice Data Storage Area 206B553 b 4a (S8). CPU 211 (FIG. 1) of Device B outputs the 1st zone enteringnotice data retrieved in the previous step from Speaker 216 (FIG. 1) andLCD 201 (FIG. 1) of Device B (S9). CPU 211 (FIG. 1) of Device Bretrieves the map data from Map Data Storage Area 206B553 b 1 (S10). CPU211 (FIG. 1) of Device B displays the map data retrieved in the previousstep on LCD 201 (FIG. 1) of Device B (S11). CPU 211 (FIG. 1) of Device Bretrieves the Device A location data from Device A Location Data StorageArea 206B553 b 3 a (S12). CPU 211 (FIG. 1) of Device B retrieves theDevice A icon image data from Device A Icon Image Data Storage Area206B553 b 5 a (S13). CPU 211 (FIG. 1) of Device B displays the Device Aicon image data retrieved in the previous step at the locationcorresponding to the Device A location data retrieved in S12 on the mapdata displayed in S11 (S14). CPU 211 (FIG. 1) of Device B retrieves theDevice B location data from Device B Location Data Storage Area 206B553b 3 b (S15). CPU 211 (FIG. 1) of Device B retrieves the Device B iconimage data from Device B Icon Image Data Storage Area 206B553 b 5 b(S16). CPU 211 (FIG. 1) of Device B displays the Device B icon imagedata retrieved in the previous step at the location corresponding to theDevice B location data retrieved in S15 on the map data displayed in S11(517). Thus, the current geographic locations of Device A and Device Bare displayed simultaneously on the map data. The foregoing sequence isrepeated periodically.

This paragraph illustrate(s) 2nd Zone Entering Notice Data OutputtingSoftware H553 c 8 of Host H and 2nd Zone Entering Notice Data OutputtingSoftware 206B553 c 8 of Device B, which output(s) the 2nd zone enteringnotice data. In this embodiment, CPU 211 (FIG. 1) of Device B sends theDevice A location data transferring request to Host H in a wirelessfashion (S1). Here, the Device A location data transferring request isthe request to transfer the Device A location data. Host H receives theDevice A location data transferring request from Device B (S2). Host Hretrieves the Device A location data from Device A Location Data StorageArea H553 b 3 a and sends the data to Device B (S3). CPU 211 (FIG. 1) ofDevice B receives the Device A location data from Host H in a wirelessfashion and stores the data in Device A Location Data Storage Area206B553 b 3 a (S4). CPU 211 (FIG. 1) of Device B retrieves the Device Alocation data from Device A Location Data Storage Area 206B553 b 3 a(S5). CPU 211 (FIG. 1) of Device B retrieves the 2nd zone data from 2ndZone Data Storage Area 206B553 b 2 b (S6). If the Device A location dataretrieved in S5 is located inside of the 2nd zone data retrieved in theprevious step, CPU 211 (FIG. 1) of Device B proceeds to the next step(S7). CPU 211 (FIG. 1) of Device B retrieves the 2nd zone enteringnotice data from 2nd Zone Entering Notice Data Storage Area 206B553 b 4b (S8). CPU 211 (FIG. 1) of Device B outputs the 2nd zone enteringnotice data retrieved in the previous step from Speaker 216 (FIG. 1) andLCD 201 (FIG. 1) of Device B (S9). CPU 211 (FIG. 1) of Device Bretrieves the map data from Map Data Storage Area 206B553 b 1 (S10). CPU211 (FIG. 1) of Device B displays the map data retrieved in the previousstep on LCD 201 (FIG. 1) of Device B (S11). CPU 211 (FIG. 1) of Device Bretrieves the Device A location data from Device A Location Data StorageArea 206B553 b 3 a (S12). CPU 211 (FIG. 1) of Device B retrieves theDevice A icon image data from Device A Icon Image Data Storage Area206B553 b 5 a (S13). CPU 211 (FIG. 1) of Device B displays the Device Aicon image data retrieved in the previous step at the locationcorresponding to the Device A location data retrieved in S12 on the mapdata displayed in S11 (S14). CPU 211 (FIG. 1) of Device B retrieves theDevice B location data from Device B Location Data Storage Area 206B553b 3 b (S15). CPU 211 (FIG. 1) of Device B retrieves the Device B iconimage data from Device B Icon Image Data Storage Area 206B553 b 5 b(S16). CPU 211 (FIG. 1) of Device B displays the Device B icon imagedata retrieved in the previous step at the location corresponding to theDevice B location data retrieved in S15 on the map data displayed in S11(S17). Thus, the current geographic locations of Device A and Device Bare displayed simultaneously on the map data. The foregoing sequence isrepeated periodically.

This paragraph illustrate(s) 3rd Zone Entering Notice Data OutputtingSoftware H553 c 9 of Host H and 3rd Zone Entering Notice Data OutputtingSoftware 206B553 c 9 of Device B, which output(s) the 3rd zone enteringnotice data. In this embodiment, CPU 211 (FIG. 1) of Device B retrievesthe Device B location data from Device B Location Data Storage Area206B553 b 3 b (S1). CPU 211 (FIG. 1) of Device B retrieves the 3rd zonedata from 3rd Zone Data Storage Area 206B553 b 2 c (S2). If the Device Blocation data retrieved in S1 is located inside of the 3rd zone dataretrieved in the previous step, CPU 211 (FIG. 1) of Device B proceeds tothe next step (S3). CPU 211 (FIG. 1) of Device B retrieves the 3rd zoneentering notice data from 3rd Zone Entering Notice Data Storage Area206B553 b 4 c (S4). CPU 211 (FIG. 1) of Device B outputs the 3rd zoneentering notice data retrieved in the previous step from Speaker 216(FIG. 1) and LCD 201 (FIG. 1) of Device B (S5). CPU 211 (FIG. 1) ofDevice B retrieves the map data from Map Data Storage Area 206B553 b 1(S6). CPU 211 (FIG. 1) of Device B displays the map data retrieved inthe previous step on LCD 201 (FIG. 1) of Device B (S7). CPU 211 (FIG. 1)of Device B sends the Device A location data transferring request toHost H in a wireless fashion (S8). Here, the Device A location datatransferring request is the request to transfer the Device A locationdata. Host H receives the Device A location data transferring requestfrom Device B (S9). Host H retrieves the Device A location data fromDevice A Location Data Storage Area H553 b 3 a and sends the data toDevice B (S10). CPU 211 (FIG. 1) of Device B receives the Device Alocation data from Host H in a wireless fashion and stores the data inDevice A Location Data Storage Area 206B553 b 3 a (S11). CPU 211(FIG. 1) of Device B retrieves the Device A location data from Device ALocation Data Storage Area 206B553 b 3 a (S12). CPU 211 (FIG. 1) ofDevice B retrieves the Device A icon image data from Device A Icon ImageData Storage Area 206B553 b 5 a (S13). CPU 211 (FIG. 1) of Device Bdisplays the Device A icon image data retrieved in the previous step atthe location corresponding to the Device A location data retrieved inS12 on the map data displayed in S7 (S14). CPU 211 (FIG. 1) of Device Bretrieves the Device B location data from Device B Location Data StorageArea 206B553 b 3 b (S15). CPU 211 (FIG. 1) of Device B retrieves theDevice B icon image data from Device B Icon Image Data Storage Area206B553 b 5 b (S16). CPU 211 (FIG. 1) of Device B displays the Device Bicon image data retrieved in the previous step at the locationcorresponding to the Device B location data retrieved in S15 on the mapdata displayed in S7 (S17). Thus, the current geographic locations ofDevice A and Device B are displayed simultaneously on the map data. Theforegoing sequence is repeated periodically.

This paragraph illustrate(s) 4th Zone Entering Notice Data OutputtingSoftware H553 c 10 of Host H and 4th Zone Entering Notice DataOutputting Software 206B553 c 10 of Device B, which output(s) the 4thzone entering notice data. In this embodiment, CPU 211 (FIG. 1) ofDevice B retrieves the Device B location data from Device B LocationData Storage Area 206B553 b 3 b (S1). CPU 211 (FIG. 1) of Device Bretrieves the 4th zone data from 4th Zone Data Storage Area 206B553 b 2d (S2). If the Device B location data retrieved in S1 is located insideof the 4th zone data retrieved in the previous step, CPU 211 (FIG. 1) ofDevice B proceeds to the next step (S3). CPU 211 (FIG. 1) of Device Bretrieves the 4th zone entering notice data from 4th Zone EnteringNotice Data Storage Area 206B553 b 4 d (S4). CPU 211 (FIG. 1) of DeviceB outputs the 4th zone entering notice data retrieved in the previousstep from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B (S5).CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B553 b 1 (S6). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S7). CPU 211 (FIG. 1) of Device B sends the Device A location datatransferring request to Host H in a wireless fashion (S8). Here, theDevice A location data transferring request is the request to transferthe Device A location data. Host H receives the Device A location datatransferring request from Device B (S9). Host H retrieves the Device Alocation data from Device A Location Data Storage Area H553 b 3 a andsends the data to Device B (S10). CPU 211 (FIG. 1) of Device B receivesthe Device A location data from Host H in a wireless fashion and storesthe data in Device A Location Data Storage Area 206B553 b 3 a (S11). CPU211 (FIG. 1) of Device B retrieves the Device A location data fromDevice A Location Data Storage Area 206B553 b 3 a (S12). CPU 211(FIG. 1) of Device B retrieves the Device A icon image data from DeviceA Icon Image Data Storage Area 206B553 b 5 a (S13). CPU 211 (FIG. 1) ofDevice B displays the Device A icon image data retrieved in the previousstep at the location corresponding to the Device A location dataretrieved in S12 on the map data displayed in S7 (S14). CPU 211 (FIG. 1)of Device B retrieves the Device B location data from Device B LocationData Storage Area 206B553 b 3 b (S15). CPU 211 (FIG. 1) of Device Bretrieves the Device B icon image data from Device B Icon Image DataStorage Area 206B553 b 5 b (S16). CPU 211 (FIG. 1) of Device B displaysthe Device B icon image data retrieved in the previous step at thelocation corresponding to the Device B location data retrieved in S15 onthe map data displayed in S7 (S17). Thus, the current geographiclocations of Device A and Device B are displayed simultaneously on themap data. The foregoing sequence is repeated periodically.

The following paragraphs illustrate another embodiment wherein Device Aplays the major role in implementing the present function.

This paragraph illustrate(s) 1st Zone Data Producing Software 206A553 c1 of Device A, which produce(s) the 1st zone data. In this embodiment,CPU 211 (FIG. 1) of Device A retrieves the map data from Map DataStorage Area 206A553 b 1 (S1). CPU 211 (FIG. 1) of Device A displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Aproduces the 1st zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device A stores the 1st zonedata produced in the previous step in 1st Zone Data Storage Area 206A553b 2 a (S5).

This paragraph illustrate(s) 2nd Zone Data Producing Software 206A553 c2 of Device A, which produces) the 2nd zone data. In this embodiment,CPU 211 (FIG. 1) of Device A retrieves the map data from Map DataStorage Area 206A553 b 1 (S1). CPU 211 (FIG. 1) of Device A displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Aproduces the 2nd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device A stores the 2nd zonedata produced in the previous step in 2nd Zone Data Storage Area 206A553b 2 b (S5).

This paragraph illustrate(s) 3rd Zone Data Producing Software 206A553 c3 of Device A, which produce(s) the 3rd zone data. In this embodiment,CPU 211 (FIG. 1) of Device A retrieves the map data from Map DataStorage Area 206A553 b 1 (S1). CPU 211 (FIG. 1) of Device A displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Aproduces the 3rd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device A stores the 3rd zonedata produced in the previous step in 3rd Zone Data Storage Area 206A553b 2 c (S5).

This paragraph illustrate(s) 4th Zone Data Producing Software 206A553 c4 of Device A, which produce(s) the 4th zone data. In this embodiment,CPU 211 (FIG. 1) of Device A retrieves the map data from Map DataStorage Area 206A553 b 1 (S1). CPU 211 (FIG. 1) of Device A displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device A(S2). The user of Device A selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Aproduces the 4th zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device A stores the 4th zonedata produced in the previous step in 4th Zone Data Storage Area 206A553b 2 d (S5).

This paragraph illustrate(s) 1st Zone Data Producing Software 206B553 c1 of Device B, which produce(s) the 1st zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B553 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 1st zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 1st zonedata produced in the previous step in 1st Zone Data Storage Area 206B553b 2 a (S5).

This paragraph illustrate(s) 2nd Zone Data Producing Software 206B553 c2 of Device B, which produce(s) the 2nd zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B553 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 2nd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 2nd zonedata produced in the previous step in 2nd Zone Data Storage Area 206B553b 2 b (S5).

This paragraph illustrate(s) 3rd Zone Data Producing Software 206B553 c3 of Device B, which produce(s) the 3rd zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B553 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 3rd zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 3rd zonedata produced in the previous step in 3rd Zone Data Storage Area 206B553b 2 c (S5).

This paragraph illustrate(s) 4th Zone Data Producing Software 206B553 c4 of Device B, which produce(s) the 4th zone data. In this embodiment,CPU 211 (FIG. 1) of Device B retrieves the map data from Map DataStorage Area 206B553 b 1 (S1). CPU 211 (FIG. 1) of Device B displays themap data retrieved in the previous step on LCD 201 (FIG. 1) of Device B(S2). The user of Device B selects, by utilizing Input Device 210(FIG. 1) or via voice recognition system, a specific zone on the mapdata displayed in the previous step (S3). CPU 211 (FIG. 1) of Device Bproduces the 4th zone data by referring to the specific zone selected inthe previous step (S4). CPU 211 (FIG. 1) of Device B stores the 4th zonedata produced in the previous step in 4th Zone Data Storage Area 206B553b 2 d (S5).

This paragraph illustrate(s) Device A Location Data Producing Software206A553 c 5 of Device A, which produce(s) Device A location data. Inthis embodiment, CPU 211 (FIG. 1) of Device A identifies the currentlocation of Device A (S1). CPU 211 (FIG. 1) of Device A produces theDevice A location data by utilizing the current location identified inthe previous step (S2). CPU 211 (FIG. 1) of Device A stores the Device Alocation data produced in the previous step in Device A Location DataStorage Area 206A553 b 3 a (S3). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) Device B Location Data Producing Software206B553 c 6 of Device B, which produce(s) Device B location data. Inthis embodiment, CPU 211 (FIG. 1) of Device B identifies the currentlocation of Device B (S1). CPU 211 (FIG. 1) of Device B produces theDevice B location data by utilizing the current location identified inthe previous step (S2). CPU 211 (FIG. 1) of Device B stores the Device Blocation data produced in the previous step in Device B Location DataStorage Area 206B553 b 3 b (S3). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 1st Zone Entering Notice Data OutputtingSoftware 206A553 c 7 of Device A and 1st Zone Entering Notice DataOutputting Software 206B553 c 7 of Device B, which output(s) the 1stzone entering notice data. In this embodiment, CPU 211 (FIG. 1) ofDevice A retrieves the Device A location data from Device A LocationData Storage Area 206A553 b 3 a (S1). CPU 211 (FIG. 1) of Device Aretrieves the 1st zone data from 1st Zone Data Storage Area 206A553 b 2a (S2). If the Device A location data retrieved in 51 is located insideof the 1st zone data retrieved in the previous step, CPU 211 (FIG. 1) ofDevice A proceeds to the next step (S3). CPU 211 (FIG. 1) of Device Aretrieves the 1st zone entering notice data from 1st Zone EnteringNotice Data Storage Area 206A553 b 4 a (S4). CPU 211 (FIG. 1) of DeviceA outputs the 1st zone entering notice data retrieved in the previousstep from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device A (S5).CPU 211 (FIG. 1) of Device A sends the Device B location datatransferring request to Device B in a wireless fashion (S6). Here, theDevice B location data transferring request is the request to transferthe Device B location data. CPU 211 (FIG. 1) of Device B receives theDevice B location data transferring request from Device A in a wirelessfashion (S7). CPU 211 (FIG. 1) of Device B retrieves the Device Blocation data from Device B Location Data Storage Area 206B553 b 3 b andsends the data to Device A in a wireless fashion (S8). CPU 211 (FIG. 1)of Device A receives the Device B location data from Device B in awireless fashion and stores the data in Device B Location Data StorageArea 206A553 b 3 b (S9). CPU 211 (FIG. 1) of Device A retrieves the mapdata from Map Data Storage Area 206A553 b 1 (S10). CPU 211 (FIG. 1) ofDevice A displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device A (S11). CPU 211 (FIG. 1) of Device A retrieves theDevice A location data from Device A Location Data Storage Area 206A553b 3 a (S12). CPU 211 (FIG. 1) of Device A retrieves the Device A iconimage data from Device A Icon Image Data Storage Area 206A553 b 5 a(S13). CPU 211 (FIG. 1) of Device A displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device A retrieves the Device B location datafrom Device B Location Data Storage Area 206A553 b 3 b (S15). CPU 211(FIG. 1) of Device A retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206A553 b 5 b (S16). CPU 211 (FIG. 1) ofDevice A displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Zone Entering Notice Data OutputtingSoftware 206A553 c 8 of Device A and 2nd Zone Entering Notice DataOutputting Software 206B553 c 8 of Device B, which output(s) the 2ndzone entering notice data. In this embodiment, CPU 211 (FIG. 1) ofDevice A retrieves the Device A location data from Device A LocationData Storage Area 206A553 b 3 a (S1). CPU 211 (FIG. 1) of Device Aretrieves the 2nd zone data from 2nd Zone Data Storage Area 206A553 b 2b (S2). If the Device A location data retrieved in S1 is located insideof the 2nd zone data retrieved in the previous step, CPU 211 (FIG. 1) ofDevice A proceeds to the next step (S3). CPU 211 (FIG. 1) of Device Aretrieves the 2nd zone entering notice data from 2nd Zone EnteringNotice Data Storage Area 206A553 b 4 b (S4). CPU 211 (FIG. 1) of DeviceA outputs the 2nd zone entering notice data retrieved in the previousstep from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device A (S5).CPU 211 (FIG. 1) of Device A sends the Device B location datatransferring request to Device B in a wireless fashion (S6). Here, theDevice B location data transferring request is the request to transferthe Device B location data. CPU 211 (FIG. 1) of Device B receives theDevice B location data transferring request from Device A in a wirelessfashion (S7). CPU 211 (FIG. 1) of Device B retrieves the Device Blocation data from Device B Location Data Storage Area 206B553 b 3 b andsends the data to Device A in a wireless fashion (S8). CPU 211 (FIG. 1)of Device A receives the Device B location data from Device B in awireless fashion and stores the data in Device B Location Data StorageArea 206A553 b 3 b (S9). CPU 211 (FIG. 1) of Device A retrieves the mapdata from Map Data Storage Area 206A553 b 1 (S10). CPU 211 (FIG. 1) ofDevice A displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device A (S11). CPU 211 (FIG. 1) of Device A retrieves theDevice A location data from Device A Location Data Storage Area 206A553b 3 a (S12). CPU 211 (FIG. 1) of Device A retrieves the Device A iconimage data from Device A Icon Image Data Storage Area 206A553 b 5 a(S13). CPU 211 (FIG. 1) of Device A displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device A retrieves the Device B location datafrom Device B Location Data Storage Area 206A553 b 3 b (S15). CPU 211(FIG. 1) of Device A retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206A553 b 5 b (S16). CPU 211 (FIG. 1) ofDevice A displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 3rd Zone Entering Notice Data OutputtingSoftware 206A553 c 9 of Device A and 3rd Zone Entering Notice DataOutputting Software 206B553 c 9 of Device B, which output(s) the 3rdzone entering notice data. In this embodiment, CPU 211 (FIG. 1) ofDevice A sends the Device B location data transferring request to DeviceB in a wireless fashion (S1). Here, the Device B location datatransferring request is the request to transfer the Device B locationdata. CPU 211 (FIG. 1) of Device B receives the Device B location datatransferring request from Device A in a wireless fashion (S2). CPU 211(FIG. 1) of Device B retrieves the Device B location data from Device BLocation Data Storage Area 206B553 b 3 b and sends the data to Device Ain a wireless fashion (S3). CPU 211 (FIG. 1) of Device A receives theDevice B location data from Device B in a wireless fashion and storesthe data in Device B Location Data Storage Area 206A553 b 3 b (S4). CPU211 (FIG. 1) of Device A retrieves the Device B location data fromDevice B Location Data Storage Area 206A553 b 3 b (S5). CPU 211 (FIG. 1)of Device A retrieves the 3rd zone data from 3rd Zone Data Storage Area206A553 b 2 c (S6). If the Device B location data retrieved in S5 islocated inside of the 3rd zone data retrieved in the previous step, CPU211 (FIG. 1) of Device A proceeds to the next step (S7). CPU 211(FIG. 1) of Device A retrieves the 3rd zone entering notice data from3rd Zone Entering Notice Data Storage Area 206A553 b 4 c (S8). CPU 211(FIG. 1) of Device A outputs the 3rd zone entering notice data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice A (S9). CPU 211 (FIG. 1) of Device A retrieves the map data fromMap Data Storage Area 206A553 b 1 (S10). CPU 211 (FIG. 1) of Device Adisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device A (S11). CPU 211 (FIG. 1) of Device A retrieves the Device Alocation data from Device A Location Data Storage Area 206A553 b 3 a(S12). CPU 211 (FIG. 1) of Device A retrieves the Device A icon imagedata from Device A Icon Image Data Storage Area 206A553 b 5 a (S13). CPU211 (FIG. 1) of Device A displays the Device A icon image data retrievedin the previous step at the location corresponding to the Device Alocation data retrieved in S12 on the map data displayed in S11 (S14).CPU 211 (FIG. 1) of Device A retrieves the Device B location data fromDevice B Location Data Storage Area 206A553 b 3 b (S15). CPU 211(FIG. 1) of Device A retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206A553 b 5 b (S16). CPU 211 (FIG. 1) ofDevice A displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 4th Zone Entering Notice Data OutputtingSoftware 206A553 c 10 of Device A and 4th Zone Entering Notice DataOutputting Software 206B553 c 10 of Device B, which output(s) the 4thzone entering notice data. In this embodiment, CPU 211 (FIG. 1) ofDevice A sends the Device B location data transferring request to DeviceB in a wireless fashion (S1). Here, the Device B location datatransferring request is the request to transfer the Device B locationdata. CPU 211 (FIG. 1) of Device B receives the Device B location datatransferring request from Device A in a wireless fashion (S2). CPU 211(FIG. 1) of Device B retrieves the Device B location data from Device BLocation Data Storage Area 206B553 b 3 b and sends the data to Device Ain a wireless fashion (S3). CPU 211 (FIG. 1) of Device A receives theDevice B location data from Device B in a wireless fashion and storesthe data in Device B Location Data Storage Area 206A553 b 3 b (S4). CPU211 (FIG. 1) of Device A retrieves the Device B location data fromDevice B Location Data Storage Area 206A553 b 3 b (S5). CPU 211 (FIG. 1)of Device A retrieves the 4th zone data from 4th Zone Data Storage Area206A553 b 2 d (S6). If the Device B location data retrieved in S5 islocated inside of the 4th zone data retrieved in the previous step, CPU211 (FIG. 1) of Device A proceeds to the next step (S7). CPU 211(FIG. 1) of Device A retrieves the 4th zone entering notice data from4th Zone Entering Notice Data Storage Area 206A553 b 4 d (S8). CPU 211(FIG. 1) of Device A outputs the 4th zone entering notice data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice A (S9). CPU 211 (FIG. 1) of Device A retrieves the map data fromMap Data Storage Area 206A553 b 1 (S10). CPU 211 (FIG. 1) of Device Adisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device A (S11). CPU 211 (FIG. 1) of Device A retrieves the Device Alocation data from Device A Location Data Storage Area 206A553 b 3 a(S12). CPU 211 (FIG. 1) of Device A retrieves the Device A icon imagedata from Device A Icon Image Data Storage Area 206A553 b 5 a (S13). CPU211 (FIG. 1) of Device A displays the Device A icon image data retrievedin the previous step at the location corresponding to the Device Alocation data retrieved in S12 on the map data displayed in S11 (S14).CPU 211 (FIG. 1) of Device A retrieves the Device B location data fromDevice B Location Data Storage Area 206A553 b 3 b (S15). CPU 211(FIG. 1) of Device A retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206A553 b 5 b (S16). CPU 211 (FIG. 1) ofDevice A displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 1st Zone Entering Notice Data OutputtingSoftware 206A553 c 7 of Device A and 1st Zone Entering Notice DataOutputting Software 206B553 c 7 of Device B, which output(s) the 1stzone entering notice data. In this embodiment, CPU 211 (FIG. 1) ofDevice B sends the Device A location data transferring request to DeviceA in a wireless fashion (S1). Here, the Device A location datatransferring request is the request to transfer the Device A locationdata. CPU 211 (FIG. 1) of Device A receives the Device A location datatransferring request from Device B in a wireless fashion (S2). CPU 211(FIG. 1) of Device A retrieves the Device A location data from Device ALocation Data Storage Area 206A553 b 3 a and sends the data to Device Bin a wireless fashion (S3). CPU 211 (FIG. 1) of Device B receives theDevice A location data from Device A in a wireless fashion and storesthe data in Device A Location Data Storage Area 206B553 b 3 a (S4). CPU211 (FIG. 1) of Device B retrieves the Device A location data fromDevice A Location Data Storage Area 206B553 b 3 a (S5). CPU 211 (FIG. 1)of Device B retrieves the 1st zone data from 1st Zone Data Storage Area206B553 b 2 a (S6). If the Device A location data retrieved in S5 islocated inside of the 1st zone data retrieved in the previous step, CPU211 (FIG. 1) of Device B proceeds to the next step (S7). CPU 211(FIG. 1) of Device B retrieves the 1st zone entering notice data from1st Zone Entering Notice Data Storage Area 206B553 b 4 a (S8). CPU 211(FIG. 1) of Device B outputs the 1st zone entering notice data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice B (S9). CPU 211 (FIG. 1) of Device B retrieves the map data fromMap Data Storage Area 206B553 b 1 (S10). CPU 211 (FIG. 1) of Device Bdisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device B (S11). CPU 211 (FIG. 1) of Device B retrieves the Device Blocation data from Device B Location Data Storage Area 206B553 b 3 b(S12). CPU 211 (FIG. 1) of Device B retrieves the Device B icon imagedata from Device B Icon Image Data Storage Area 206B553 b 5 b (S13). CPU211 (FIG. 1) of Device B displays the Device B icon image data retrievedin the previous step at the location corresponding to the Device Blocation data retrieved in S12 on the map data displayed in S11 (S14).CPU 211 (FIG. 1) of Device B retrieves the Device A location data fromDevice A Location Data Storage Area 206B553 b 3 a (S15). CPU 211(FIG. 1) of Device B retrieves the Device A icon image data from DeviceA Icon Image Data Storage Area 206B553 b 5 a (S16). CPU 211 (FIG. 1) ofDevice B displays the Device A icon image data retrieved in the previousstep at the location corresponding to the Device A location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Zone Entering Notice Data OutputtingSoftware 206A553 c 8 of Device A and 2nd Zone Entering Notice DataOutputting Software 206B553 c 8 of Device B, which output(s) the 2ndzone entering notice data. In this embodiment, CPU 211 (FIG. 1) ofDevice B sends the Device A location data transferring request to DeviceA in a wireless fashion (S1). Here, the Device A location datatransferring request is the request to transfer the Device A locationdata. CPU 211 (FIG. 1) of Device A receives the Device A location datatransferring request from Device B in a wireless fashion (S2). CPU 211(FIG. 1) of Device A retrieves the Device A location data from Device ALocation Data Storage Area 206A553 b 3 a and sends the data to Device Bin a wireless fashion (S3). CPU 211 (FIG. 1) of Device B receives theDevice A location data from Device A in a wireless fashion and storesthe data in Device A Location Data Storage Area 206B553 b 3 a (S4). CPU211 (FIG. 1) of Device B retrieves the Device A location data fromDevice A Location Data Storage Area 206B553 b 3 a (S5). CPU 211 (FIG. 1)of Device B retrieves the 2nd zone data from 2nd Zone Data Storage Area206B553 b 2 b (S6). If the Device A location data retrieved in S5 islocated inside of the 2nd zone data retrieved in the previous step, CPU211 (FIG. 1) of Device B proceeds to the next step (S7). CPU 211(FIG. 1) of Device B retrieves the 2nd zone entering notice data from2nd Zone Entering Notice Data Storage Area 206B553 b 4 b (S8). CPU 211(FIG. 1) of Device B outputs the 2nd zone entering notice data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice B (S9). CPU 211 (FIG. 1) of Device B retrieves the map data fromMap Data Storage Area 206B553 b 1 (S10). CPU 211 (FIG. 1) of Device Bdisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device B (S11). CPU 211 (FIG. 1) of Device B retrieves the Device Blocation data from Device B Location Data Storage Area 206B553 b 3 b(S12). CPU 211 (FIG. 1) of Device B retrieves the Device B icon imagedata from Device B Icon Image Data Storage Area 206B553 b 5 b (S13). CPU211 (FIG. 1) of Device B displays the Device B icon image data retrievedin the previous step at the location corresponding to the Device Blocation data retrieved in S12 on the map data displayed in S11 (S14).CPU 211 (FIG. 1) of Device B retrieves the Device A location data fromDevice A Location Data Storage Area 206B553 b 3 a (S15). CPU 211(FIG. 1) of Device B retrieves the Device A icon image data from DeviceA Icon Image Data Storage Area 206B553 b 5 a (S16). CPU 211 (FIG. 1) ofDevice B displays the Device A icon image data retrieved in the previousstep at the location corresponding to the Device A location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 3rd Zone Entering Notice Data OutputtingSoftware 206A553 c 9 of Device A and 3rd Zone Entering Notice DataOutputting Software 206B553 c 9 of Device B, which output(s) the 3rdzone entering notice data. In this embodiment, CPU 211 (FIG. 1) ofDevice B retrieves the Device B location data from Device B LocationData Storage Area 206B553 b 3 b (S1). CPU 211 (FIG. 1) of Device Bretrieves the 3rd zone data from 3rd Zone Data Storage Area 206B553 b 2c (S2). If the Device B location data retrieved in 51 is located insideof the 3rd zone data retrieved in the previous step, CPU 211 (FIG. 1) ofDevice B proceeds to the next step (S3). CPU 211 (FIG. 1) of Device Bretrieves the 3rd zone entering notice data from 3rd Zone EnteringNotice Data Storage Area 206B553 b 4 c (S4). CPU 211 (FIG. 1) of DeviceB outputs the 3rd zone entering notice data retrieved in the previousstep from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B (S5).CPU 211 (FIG. 1) of Device B sends the Device A location datatransferring request to Device A in a wireless fashion (S6). Here, theDevice A location data transferring request is the request to transferthe Device A location data. CPU 211 (FIG. 1) of Device A receives theDevice A location data transferring request from Device B in a wirelessfashion (S7). CPU 211 (FIG. 1) of Device A retrieves the Device Alocation data from Device A Location Data Storage Area 206A553 b 3 a andsends the data to Device B in a wireless fashion (S8). CPU 211 (FIG. 1)of Device B receives the Device A location data from Device A in awireless fashion and stores the data in Device A Location Data StorageArea 206B553 b 3 a (S9). CPU 211 (FIG. 1) of Device B retrieves the mapdata from Map Data Storage Area 206B553 b 1 (S10). CPU 211 (FIG. 1) ofDevice B displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device B (S11). CPU 211 (FIG. 1) of Device B retrieves theDevice A location data from Device A Location Data Storage Area 206B553b 3 a (S12). CPU 211 (FIG. 1) of Device B retrieves the Device A iconimage data from Device A Icon Image Data Storage Area 206B553 b 5 a(S13). CPU 211 (FIG. 1) of Device B displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B553 b 3 b (S15). CPU 211(FIG. 1) of Device B retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206B553 b 5 b (S16). CPU 211 (FIG. 1) ofDevice B displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 4th Zone Entering Notice Data OutputtingSoftware 206A553 c 10 of Device A and 4th Zone Entering Notice DataOutputting Software 206B553 c 10 of Device B, which output(s) the 4thzone entering notice data. In this embodiment, CPU 211 (FIG. 1) ofDevice B retrieves the Device B location data from Device B LocationData Storage Area 206B553 b 3 b (S1). CPU 211 (FIG. 1) of Device Bretrieves the 4th zone data from 4th Zone Data Storage Area 206B553 b 2d (S2). If the Device B location data retrieved in 51 is located insideof the 4th zone data retrieved in the previous step, CPU 211 (FIG. 1) ofDevice B proceeds to the next step (S3). CPU 211 (FIG. 1) of Device Bretrieves the 4th zone entering notice data from 4th Zone EnteringNotice Data Storage Area 206B553 b 4 d (S4). CPU 211 (FIG. 1) of DeviceB outputs the 4th zone entering notice data retrieved in the previousstep from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B (S5).CPU 211 (FIG. 1) of Device B sends the Device A location datatransferring request to Device A in a wireless fashion (S6). Here, theDevice A location data transferring request is the request to transferthe Device A location data. CPU 211 (FIG. 1) of Device A receives theDevice A location data transferring request from Device B in a wirelessfashion (S7). CPU 211 (FIG. 1) of Device A retrieves the Device Alocation data from Device A Location Data Storage Area 206A553 b 3 a andsends the data to Device B in a wireless fashion (S8). CPU 211 (FIG. 1)of Device B receives the Device A location data from Device A in awireless fashion and stores the data in Device A Location Data StorageArea 206B553 b 3 a (S9). CPU 211 (FIG. 1) of Device B retrieves the mapdata from Map Data Storage Area 206B553 b 1 (S10). CPU 211 (FIG. 1) ofDevice B displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device B (S11). CPU 211 (FIG. 1) of Device B retrieves theDevice A location data from Device A Location Data Storage Area 206B553b 3 a (S12). CPU 211 (FIG. 1) of Device B retrieves the Device A iconimage data from Device A Icon Image Data Storage Area 206B553 b 5 a(S13). CPU 211 (FIG. 1) of Device B displays the Device A icon imagedata retrieved in the previous step at the location corresponding to theDevice A location data retrieved in S12 on the map data displayed in S11(S14). CPU 211 (FIG. 1) of Device B retrieves the Device B location datafrom Device B Location Data Storage Area 206B553 b 3 b (S15). CPU 211(FIG. 1) of Device B retrieves the Device B icon image data from DeviceB Icon Image Data Storage Area 206B553 b 5 b (S16). CPU 211 (FIG. 1) ofDevice B displays the Device B icon image data retrieved in the previousstep at the location corresponding to the Device B location dataretrieved in S15 on the map data displayed in S11 (S17). Thus, thecurrent geographic locations of Device A and Device B are displayedsimultaneously on the map data. The foregoing sequence is repeatedperiodically.

<<Power Off Notifying Function>>

The following paragraphs illustrate the power off notifying function,wherein when the power of Communication Device 200 is being turned off,the geographic location of Communication Device 200 is notified toanother device. The map is displayed on another device and thegeographic location of Communication Device 200 is indicated on the map.Further, the notification indicating that the power of CommunicationDevice 200 is being turned off is output from another device.

This paragraph illustrates the major elements utilized to implement thepresent function. In this embodiment, Host H is connected to Network NT(e.g., the Internet). Device A, a Communication Device 200, is connectedto Network NT (e.g., the Internet) in a wireless fashion. Device B,another Communication Device 200, is connected to Network NT (e.g., theInternet) in a wireless fashion. Host H, Device A, and Device B arecapable to communicate with each other via Network NT (e.g., theInternet) to implement the present function. Device A and Device B arealso capable to communicate with each other directly in a wirelessfashion to implement the present function.

This paragraph illustrates the storage area included in Host H. In thisembodiment, Host H includes Power Off Notifying Information Storage AreaH554 a of which the data and the software program(s) stored therein aredescribed hereinafter.

This paragraph illustrates the storage area(s) included in Power OffNotifying Information Storage Area H554 a. In this embodiment, Power OffNotifying Information Storage Area H554 a includes Power Off NotifyingData Storage Area H554 b and Power Off Notifying Software Storage AreaH554 c. Power Off Notifying Data Storage Area H554 b stores the datanecessary to implement the present function on the side of Host H, suchas the one(s) described hereinafter. Power Off Notifying SoftwareStorage Area H554 c stores the software program(s) necessary toimplement the present function on the side of Host H, such as the one(s)described hereinafter.

This paragraph illustrates the storage area(s) included in Power OffNotifying Data Storage Area H554 b. In this embodiment, Power OffNotifying Data Storage Area H554 b includes Map Data Storage Area H554 b1, Party Location Data Storage Area H554 b 2, Party Icon Image DataStorage Area H554 b 3, Device Power Off Notice Data Storage Area H554 b4, Party Location Notifying Data Storage Area H554 b 5, and Work AreaH554 b 6. Map Data Storage Area H554 b 1 stores the map data which isthe image data indicating a map. Party Location Data Storage Area H554 b2 stores the data described hereinafter. Party Icon Image Data StorageArea H554 b 3 stores the data described hereinafter. Device Power OffNotice Data Storage Area H554 b 4 stores the data described hereinafter.Party Location Notifying Data Storage Area H554 b 5 stores the datadescribed hereinafter. Work Area H554 b 6 is utilized as a work area toperform calculation and temporarily store data.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area H554 b 2. In this embodiment, Party LocationData Storage Area H554 b 2 includes 1st Location Data Storage Area H554b 2 a and 2nd Location Data Storage Area H554 b 2 b. 1st Location DataStorage Area H554 b 2 a stores the 1st location data which indicates thecurrent geographic location of Device A in (x,y,z) format. 2nd LocationData Storage Area H554 b 2 b stores the 2nd location data whichindicates the current geographic location of Device B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area H554 b 3. In this embodiment, Party Icon ImageData Storage Area H554 b 3 includes 1st Icon Image Data Storage AreaH554 b 3 a and 2nd Icon Image Data Storage Area H554 b 3 b. 1st IconImage Data Storage Area H554 b 3 a stores the 1st icon image data whichis the image data of the icon indicating the current geographic locationof Device A on the map data. 2nd Icon Image Data Storage Area H554 b 3 bstores the 2nd icon image data which is the image data of the iconindicating the current geographic location of Device B on the map data.

This paragraph illustrates the storage area(s) included in Device PowerOff Notice Data Storage Area H554 b 4. In this embodiment, Device PowerOff Notice Data Storage Area H554 b 4 includes 1st Power Off Notice DataStorage Area H554 b 4 a and 2nd Power Off Notice Data Storage Area H554b 4 b. 1st Power Off Notice Data Storage Area H554 b 4 a stores the 1stpower off notice data which is the audiovisual data indicating that thepower of Device A is turned off 2nd Power Off Notice Data Storage AreaH554 b 4 b stores the 2nd power off notice data which is the audiovisualdata indicating that the power of Device B is turned off.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area H554 b 5. In this embodiment, PartyLocation Notifying Data Storage Area H554 b 5 includes 1st LocationNotifying Data Storage Area H554 b 5 a and 2nd Location Notifying DataStorage Area H554 b 5 b. 1st Location Notifying Data Storage Area H554 b5 a stores the 1st location notifying data which is the audiovisual datanotifying that the current geographic location of Device A is displayedon Device B. 2nd Location Notifying Data Storage Area H554 b 5 b storesthe 2nd location notifying data which is the audiovisual data notifyingthat the current geographic location of Device B is displayed on DeviceA.

This paragraph illustrates the software program(s) stored in Power OffNotifying Software Storage Area H554 c. In this embodiment, Power OffNotifying Software Storage Area H554 c stores 1st Location DataProducing Software H554 c 1, 1st Power Off Notice Data OutputtingSoftware H554 c 3, 2nd Power Off Notice Data Outputting Software H554 c4, 1st Location Data Displaying Software H554 c 5, and 2nd Location DataDisplaying Software H554 c 6. 1st Location Data Producing Software H554c 1 is the software program described hereinafter. 1st Power Off NoticeData Outputting Software H554 c 3 is the software program describedhereinafter. 2nd Power Off Notice Data Outputting Software H554 c 4 isthe software program described hereinafter. 1st Location Data DisplayingSoftware H554 c 5 is the software program described hereinafter. 2ndLocation Data Displaying Software H554 c 6 is the software programdescribed hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device A. In this embodiment, RAM 206 includes Power Off NotifyingInformation Storage Area 206A554 a of which the data and the softwareprogram(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device A.

This paragraph illustrates the storage area(s) included in Power OffNotifying Information Storage Area 206A554 a. In this embodiment, PowerOff Notifying Information Storage Area 206A554 a includes Power OffNotifying Data Storage Area 206A554 b and Power Off Notifying SoftwareStorage Area 206A554 c. Power Off Notifying Data Storage Area 206A554 bstores the data necessary to implement the present function on the sideof Device A, such as the one(s) described hereinafter. Power OffNotifying Software Storage Area 206A554 c stores the software program(s)necessary to implement the present function on the side of Device A,such as the one(s) described hereinafter.

This paragraph illustrates the storage area(s) included in Power OffNotifying Data Storage Area 206A554 b. In this embodiment, Power OffNotifying Data Storage Area 206A554 b includes Map Data Storage Area206A554 b 1, Party Location Data Storage Area 206A554 b 2, Party IconImage Data Storage Area 206A554 b 3, Device Power Off Notice DataStorage Area 206A554 b 4, Party Location Notifying Data Storage Area206A554 b 5, and Work Area 206A554 b 6. Map Data Storage Area 206A554 b1 stores the map data which is the image data indicating a map. PartyLocation Data Storage Area 206A554 b 2 stores the data describedhereinafter. Party Icon Image Data Storage Area 206A554 b 3 stores thedata described hereinafter. Device Power Off Notice Data Storage Area206A554 b 4 stores the data described hereinafter. Party LocationNotifying Data Storage Area 206A554 b 5 stores the data describedhereinafter. Work Area 206A554 b 6 is utilized as a work area to performcalculation and temporarily store data.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area 206A554 b 2. In this embodiment, PartyLocation Data Storage Area 206A554 b 2 includes 1st Location DataStorage Area 206A554 b 2 a and 2nd Location Data Storage Area 206A554 b2 b. 1st Location Data Storage Area 206A554 b 2 a stores the 1stlocation data which indicates the current geographic location of DeviceA in (x,y,z) format. 2nd Location Data Storage Area 206A554 b 2 b storesthe 2nd location data which indicates the current geographic location ofDevice B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area 206A554 b 3. In this embodiment, Party IconImage Data Storage Area 206A554 b 3 includes 1st Icon Image Data StorageArea 206A554 b 3 a and 2nd Icon Image Data Storage Area 206A554 b 3 b.1st Icon Image Data Storage Area 206A554 b 3 a stores the 1st icon imagedata which is the image data of the icon indicating the currentgeographic location of Device A on the map data. 2nd Icon Image DataStorage Area 206A554 b 3 b stores the 2nd icon image data which is theimage data of the icon indicating the current geographic location ofDevice B on the map data.

This paragraph illustrates the storage area(s) included in Device PowerOff Notice Data Storage Area 206A554 b 4. In this embodiment, DevicePower Off Notice Data Storage Area 206A554 b 4 includes 1st Power OffNotice Data Storage Area 206A554 b 4 a and 2nd Power Off Notice DataStorage Area 206A554 b 4 b. 1st Power Off Notice Data Storage Area206A554 b 4 a stores the 1st power off notice data which is theaudiovisual data indicating that the power of Device A is turned off 2ndPower Off Notice Data Storage Area 206A554 b 4 b stores the 2nd poweroff notice data which is the audiovisual data indicating that the powerof Device B is turned off This paragraph illustrates the storage area(s)included in Party Location Notifying Data Storage Area 206A554 b 5. Inthis embodiment, Party Location Notifying Data Storage Area 206A554 b 5includes 1st Location Notifying Data Storage Area 206A554 b 5 a and 2ndLocation Notifying Data Storage Area 206A554 b 5 b. 1st LocationNotifying Data Storage Area 206A554 b 5 a stores the 1st locationnotifying data which is the audiovisual data notifying that the currentgeographic location of Device A is displayed on Device B. 2nd LocationNotifying Data Storage Area 206A554 b 5 b stores the 2nd locationnotifying data which is the audiovisual data notifying that the currentgeographic location of Device B is displayed on Device A.

This paragraph illustrates the software program(s) stored in Power OffNotifying Software Storage Area 206A554 c. In this embodiment, Power OffNotifying Software Storage Area 206A554 c stores 1st Location DataProducing Software 206A554 c 1, 1st Power Off Notice Data OutputtingSoftware 206A554 c 3, 2nd Power Off Notice Data Outputting Software206A554 c 4, 1st Location Data Displaying Software 206A554 c 5, and 2ndLocation Data Displaying Software 206A554 c 6. 1st Location DataProducing Software 206A554 c 1 is the software program describedhereinafter. 1st Power Off Notice Data Outputting Software 206A554 c 3is the software program described hereinafter. 2nd Power Off Notice DataOutputting Software 206A554 c 4 is the software program describedhereinafter. 1st Location Data Displaying Software 206A554 c 5 is thesoftware program described hereinafter. 2nd Location Data DisplayingSoftware 206A554 c 6 is the software program described hereinafter.

This paragraph illustrates the storage area included in RAM 206 (FIG. 1)of Device B. In this embodiment, RAM 206 includes Power Off NotifyingInformation Storage Area 206B554 a of which the data and the softwareprogram(s) stored therein are described hereinafter.

The data and/or the software program(s) necessary to implement thepresent function may be downloaded from Host H to Device B.

This paragraph illustrates the storage area(s) included in Power OffNotifying Information Storage Area 206B554 a. In this embodiment, PowerOff Notifying Information Storage Area 206B554 a includes Power OffNotifying Data Storage Area 206B554 b and Power Off Notifying SoftwareStorage Area 206B554 c. Power Off Notifying Data Storage Area 206B554 bstores the data necessary to implement the present function on the sideof Device B, such as the one(s) described hereinafter. Power OffNotifying Software Storage Area 206B554 c stores the software program(s)necessary to implement the present function on the side of Device B,such as the one(s) described hereinafter.

This paragraph illustrates the storage area(s) included in Power OffNotifying Data Storage Area 206B554 b. In this embodiment, Power OffNotifying Data Storage Area 206B554 b includes Map Data Storage Area206B554 b 1, Party Location Data Storage Area 206B554 b 2, Party IconImage Data Storage Area 206B554 b 3, Device Power Off Notice DataStorage Area 206B554 b 4, Party Location Notifying Data Storage Area206B554 b 5, and Work Area 206B554 b 6. Map Data Storage Area 206B554 b1 stores the map data which is the image data indicating a map. PartyLocation Data Storage Area 206B554 b 2 stores the data describedhereinafter. Party Icon Image Data Storage Area 206B554 b 3 stores thedata described hereinafter. Device Power Off Notice Data Storage Area206B554 b 4 stores the data described hereinafter. Party LocationNotifying Data Storage Area 206B554 b 5 stores the data describedhereinafter. Work Area 206B554 b 6 is utilized as a work area to performcalculation and temporarily store data.

This paragraph illustrates the storage area(s) included in PartyLocation Data Storage Area 206B554 b 2. In this embodiment, PartyLocation Data Storage Area 206B554 b 2 includes 1st Location DataStorage Area 206B554 b 2 a and 2nd Location Data Storage Area 206B554 b2 b. 1st Location Data Storage Area 206B554 b 2 a stores the 1stlocation data which indicates the current geographic location of DeviceA in (x,y,z) format. 2nd Location Data Storage Area 206B554 b 2 b storesthe 2nd location data which indicates the current geographic location ofDevice B in (x,y,z) format.

This paragraph illustrates the storage area(s) included in Party IconImage Data Storage Area 206B554 b 3. In this embodiment, Party IconImage Data Storage Area 206B554 b 3 includes 1st Icon Image Data StorageArea 206B554 b 3 a and 2nd Icon Image Data Storage Area 206B554 b 3 b.1st Icon Image Data Storage Area 206B554 b 3 a stores the 1st icon imagedata which is the image data of the icon indicating the currentgeographic location of Device A on the map data. 2nd Icon Image DataStorage Area 206B554 b 3 b stores the 2nd icon image data which is theimage data of the icon indicating the current geographic location ofDevice B on the map data.

This paragraph illustrates the storage area(s) included in Device PowerOff Notice Data Storage Area 206B554 b 4. In this embodiment, DevicePower Off Notice Data Storage Area 206B554 b 4 includes 1st Power OffNotice Data Storage Area 206B554 b 4 a and 2nd Power Off Notice DataStorage Area 206B554 b 4 b. 1st Power Off Notice Data Storage Area206B554 b 4 a stores the 1st power off notice data which is theaudiovisual data indicating that the power of Device A is turned off 2ndPower Off Notice Data Storage Area 206B554 b 4 b stores the 2nd poweroff notice data which is the audiovisual data indicating that the powerof Device B is turned off.

This paragraph illustrates the storage area(s) included in PartyLocation Notifying Data Storage Area 206B554 b 5. In this embodiment,Party Location Notifying Data Storage Area 206B554 b 5 includes 1stLocation Notifying Data Storage Area 206B554 b 5 a and 2nd LocationNotifying Data Storage Area 206B554 b 5 b. 1st Location Notifying DataStorage Area 206B554 b 5 a stores the 1st location notifying data whichis the audiovisual data notifying that the current geographic locationof Device A is displayed on Device B. 2nd Location Notifying DataStorage Area 206B554 b 5 b stores the 2nd location notifying data whichis the audiovisual data notifying that the current geographic locationof Device B is displayed on Device A.

This paragraph illustrates the software program(s) stored in Power OffNotifying Software Storage Area 206B554 c. In this embodiment, Power OffNotifying Software Storage Area 206B554 c stores 2nd Location DataProducing Software 206B554 c 2, 1st Power Off Notice Data OutputtingSoftware 206B554 c 3, 2nd Power Off Notice Data Outputting Software206B554 c 4, 1st Location Data Displaying Software 206B554 c 5, and 2ndLocation Data Displaying Software 206B554 c 6. 2nd Location DataProducing Software 206B554 c 2 is the software program describedhereinafter. 1st Power Off Notice Data Outputting Software 206B554 c 3is the software program described hereinafter. 2nd Power Off Notice DataOutputting Software 206B554 c 4 is the software program describedhereinafter. 1st Location Data Displaying Software 206B554 c 5 is thesoftware program described hereinafter. 2nd Location Data DisplayingSoftware 206B554 c 6 is the software program described hereinafter.

This paragraph illustrate(s) 1st Location Data Producing Software H554 c1 of Host H and 1st Location Data Producing Software 206A554 c 1 ofDevice A, which produces) the 1st location data. In this embodiment, CPU211 (FIG. 1) of Device A identifies the current location of Device A(S1). CPU 211 (FIG. 1) of Device A produces the 1st location data byutilizing the current location identified in the previous step and sendsthe data to Host H in a wireless fashion (S2). Host H receives the 1stlocation data from Device A and stores the data in 1st Location DataStorage Area H554 b 2 a (S3). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Location Data Producing Software206B554 c 2 of Device B, which produce(s) the 2nd location data. In thisembodiment, CPU 211 (FIG. 1) of Device B identifies the current locationof Device B (S1). CPU 211 (FIG. 1) of Device B produces the 2nd locationdata by utilizing the current location identified in the previous step(S2). CPU 211 (FIG. 1) of Device B stores the 2nd location data producedin the previous step in 2nd Location Data Storage Area 206B554 b 2 b(S3). The foregoing sequence is repeated periodically.

This paragraph illustrate(s) 1st Power Off Notice Data OutputtingSoftware H554 c 3 of Host H, 1st Power Off Notice Data OutputtingSoftware 206A554 c 3 of Device A, and 1st Power Off Notice DataOutputting Software 206B554 c 3 of Device B, which output(s) the 1stpower off notice data. In this embodiment, CPU 211 (FIG. 1) of Device Aidentifies the current status of power management of Device A (S1). Ifthe power of Device A is in the process of being turned off, CPU 211(FIG. 1) of Device A proceeds to the next step (S2). CPU 211 (FIG. 1) ofDevice A sends the 1st power off notification to Host H in a wirelessfashion (S3). Here, the 1st power off notification indicates that DeviceA is turning off its power. Host H receives the 1st power offnotification from Device A (S4). Host H retrieves the 1st power offnotice data from 1st Power Off Notice Data Storage Area H554 b 4 a andsends the data to Device A (S5). CPU 211 (FIG. 1) of Device A receivesthe 1st power off notice data from Host H in a wireless fashion andoutputs the data from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice A (S6). Host H sends the 1st power off notification to Device B(S7). Here, the 1st power off notification indicates that Device A isturning off its power. CPU 211 (FIG. 1) of Device B receives the 1stpower off notification from Host H in a wireless fashion (S8). CPU 211(FIG. 1) of Device B retrieves the 1st power off notice data from 1stPower Off Notice Data Storage Area 206B554 b 4 a (S9). CPU 211 (FIG. 1)of Device B outputs the 1st power off notice data retrieved in theprevious step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B(S10). The foregoing sequence is repeated periodically.

This paragraph illustrate(s) 2nd Power Off Notice Data OutputtingSoftware H554 c 4 of Host H, 2nd Power Off Notice Data OutputtingSoftware 206A554 c 4 of Device A, and 2nd Power Off Notice DataOutputting Software 206B554 c 4 of Device B, which output(s) the 2ndpower off notice data. In this embodiment, CPU 211 (FIG. 1) of Device Bidentifies the current status of power management of Device B (S1). Ifthe power of Device B is in the process of being turned off, CPU 211(FIG. 1) of Device B proceeds to the next step (S2). CPU 211 (FIG. 1) ofDevice B retrieves the 2nd power off notice data from 2nd Power OffNotice Data Storage Area 206B554 b 4 b (S3). CPU 211 (FIG. 1) of DeviceB outputs the 2nd power off notice data retrieved in the previous stepfrom Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B (S4). CPU 211(FIG. 1) of Device B sends the 2nd power off notification to Host H in awireless fashion (S5). Here, the 2nd power off notification indicatesthat Device B is turning off its power. Host H receives the 2nd poweroff notification from Device B (S6). Host H retrieves the 2nd power offnotice data from 2nd Power Off Notice Data Storage Area H554 b 4 b andsends the data to Device A (S7). CPU 211 (FIG. 1) of Device A receivesthe 2nd power off notice data from Host H in a wireless fashion andoutputs the data from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice A (S8). The foregoing sequence is repeated periodically.

This paragraph illustrate(s) 1st Location Data Displaying Software H554c 5 of Host H, 1st Location Data Displaying Software 206A554 c 5 ofDevice A, and 1st Location Data Displaying Software 206B554 c 5 ofDevice B, which display(s) the 1st location data. In this embodiment,CPU 211 (FIG. 1) of Device A identifies the current status of powermanagement of Device A (S1). If the power of Device A is in the processof being turned of CPU 211 (FIG. 1) of Device A proceeds to the nextstep (S2). CPU 211 (FIG. 1) of Device A sends the 1st power offnotification to Host H in a wireless fashion (S3). Here, the 1st poweroff notification indicates that Device A is turning off its power. HostH receives the 1st power off notification from Device A (S4). Host Hretrieves the map data from Map Data Storage Area H554 b 1 and sends thedata to Device A (S5). CPU 211 (FIG. 1) of Device A receives the mapdata from Host H in a wireless fashion and displays the data on LCD 201(FIG. 1) of Device A (S6). Host H retrieves the 1st location data from1st Location Data Storage Area H554 b 2 a and sends the data to Device A(S7). CPU 211 (FIG. 1) of Device A receives the 1st location data fromHost H in a wireless fashion (S8). Host H retrieves the 1st icon imagedata from 1st Icon Image Data Storage Area H554 b 3 a and sends the datato Device A (S9). CPU 211 (FIG. 1) of Device A receives the 1st iconimage data from Host H in a wireless fashion (S10). CPU 211 (FIG. 1) ofDevice A displays the 1st icon image data received in the previous stepat the location corresponding to the 1st location data received in S8 onthe map data displayed in S6 (S11). Host H retrieves the 1st locationdata from 1st Location Data Storage Area H554 b 2 a and sends the datato Device B (S12). CPU 211 (FIG. 1) of Device B receives the 1stlocation data from Host H in a wireless fashion and stores the data in1st Location Data Storage Area 206B554 b 2 a (S13). CPU 211 (FIG. 1) ofDevice B retrieves the map data from Map Data Storage Area 206B554 b 1(S14). CPU 211 (FIG. 1) of Device B displays the map data retrieved inthe previous step on LCD 201 (FIG. 1) of Device B (S15). CPU 211(FIG. 1) of Device B retrieves the 1st location data from 1st LocationData Storage Area 206B554 b 2 a (S16). CPU 211 (FIG. 1) of Device Bretrieves the 1st icon image data from 1st Icon Image Data Storage Area206B554 b 3 a (S17). CPU 211 (FIG. 1) of Device B displays the 1st iconimage data retrieved in the previous step at the location correspondingto the 1st location data retrieved in S16 on the map data displayed inS15 (S18). CPU 211 (FIG. 1) of Device B retrieves the 1st locationnotifying data from 1st Location Notifying Data Storage Area 206B554 b 5a (S19). CPU 211 (FIG. 1) of Device B outputs the 1st location notifyingdata retrieved in the previous step from Speaker 216 (FIG. 1) and LCD201 (FIG. 1) of Device B (S20). CPU 211 (FIG. 1) of Device B sends the1st location notification to Host H in a wireless fashion (S21). Here,the 1st location notification indicates that the current geographiclocation of Device A is displayed on Device B. Host H receives the 1stlocation notification from Device B (S22). Host H retrieves the 1stlocation notifying data from 1st Location Notifying Data Storage AreaH554 b 5 a and sends the data to Device A (S23). CPU 211 (FIG. 1) ofDevice A receives the 1st location notifying data from Host H in awireless fashion and outputs the data from Speaker 216 (FIG. 1) and LCD201 (FIG. 1) of Device A (S24). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Location Data Displaying Software H554c 6 of Host H, 2nd Location Data Displaying Software 206A554 c 6 ofDevice A, and 2nd Location Data Displaying Software 206B554 c 6 ofDevice B, which display(s) the 2nd location data. In this embodiment,CPU 211 (FIG. 1) of Device B identifies the current status of powermanagement of Device B (S1). If the power of Device B is in the processof being turned of CPU 211 (FIG. 1) of Device B proceeds to the nextstep (S2). CPU 211 (FIG. 1) of Device B retrieves the map data from MapData Storage Area 206B554 b 1 (S3). CPU 211 (FIG. 1) of Device Bdisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device B (S4). CPU 211 (FIG. 1) of Device B retrieves the 2ndlocation data from 2nd Location Data Storage Area 206B554 b 2 b (S5).CPU 211 (FIG. 1) of Device B retrieves the 2nd icon image data from 2ndIcon Image Data Storage Area 206B554 b 3 b (S6). CPU 211 (FIG. 1) ofDevice B displays the 2nd icon image data retrieved in the previous stepat the location corresponding to the 2nd location data retrieved in S5on the map data displayed in S4 (S7). CPU 211 (FIG. 1) of Device Bretrieves the 2nd location data from 2nd Location Data Storage Area206B554 b 2 b and sends the data to Host H in a wireless fashion (S 8).Host H receives the 2nd location data from Device B and stores the datain 2nd Location Data Storage Area H554 b 2 b (S9). Host H retrieves themap data from Map Data Storage Area H554 b 1 and sends the data toDevice A (S10). CPU 211 (FIG. 1) of Device A receives the map data fromHost H in a wireless fashion and displays the data on LCD 201 (FIG. 1)of Device A (S11). Host H retrieves the 2nd location data from 2ndLocation Data Storage Area H554 b 2 b and sends the data to Device A(S12). CPU 211 (FIG. 1) of Device A receives the 2nd location data fromHost H in a wireless fashion (S13). Host H retrieves the 2nd icon imagedata from 2nd Icon Image Data Storage Area H554 b 3 b and sends the datato Device A (S14). CPU 211 (FIG. 1) of Device A receives the 2nd iconimage data from Host H in a wireless fashion (S15). CPU 211 (FIG. 1) ofDevice A displays the 2nd icon image data received in the previous stepat the location corresponding to the 2nd location data received in S13on the map data displayed in S11 (S16). Host H retrieves the 2ndlocation notifying data from 2nd Location Notifying Data Storage AreaH554 b 5 b and sends the data to Device A (S17). CPU 211 (FIG. 1) ofDevice A receives the 2nd location notifying data from Host H in awireless fashion and outputs the data from Speaker 216 (FIG. 1) and LCD201 (FIG. 1) of Device A (S18). Host H sends the 2nd locationnotification to Device B (S19). Here, the 2nd location notificationindicates that the current geographic location of Device B is displayedon Device A. CPU 211 (FIG. 1) of Device B receives the 2nd locationnotification from Host H in a wireless fashion (S20). CPU 211 (FIG. 1)of Device B retrieves the 2nd location notifying data from 2nd LocationNotifying Data Storage Area 206B554 b 5 b (S21). CPU 211 (FIG. 1) ofDevice B outputs the 2nd location notifying data retrieved in theprevious step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B(S22). The foregoing sequence is repeated periodically.

The following paragraphs illustrate another embodiment wherein Device Aplays the major role in implementing the present function.

This paragraph illustrate(s) 1st Location Data Producing Software206A554 c 1 of Device A, which produce(s) the 1st location data. In thisembodiment, CPU 211 (FIG. 1) of Device A identifies the current locationof Device A (S1). CPU 211 (FIG. 1) of Device A produces the 1st locationdata by utilizing the current location identified in the previous step(S2). CPU 211 (FIG. 1) of Device A stores the 1st location data producedin the previous step in 1st Location Data Storage Area 206A554 b 2 a(S3). The foregoing sequence is repeated periodically.

This paragraph illustrate(s) 2nd Location Data Producing Software206B554 c 2 of Device B, which produce(s) the 2nd location data. In thisembodiment, CPU 211 (FIG. 1) of Device B identifies the current locationof Device B (S1). CPU 211 (FIG. 1) of Device B produces the 2nd locationdata by utilizing the current location identified in the previous step(S2). CPU 211 (FIG. 1) of Device B stores the 2nd location data producedin the previous step in 2nd Location Data Storage Area 206B554 b 2 b(S3). The foregoing sequence is repeated periodically.

This paragraph illustrate(s) 1st Power Off Notice Data OutputtingSoftware 206A554 c 3 of Device A and 1st Power Off Notice DataOutputting Software 206B554 c 3 of Device B, which output(s) the 1stpower off notice data. In this embodiment, CPU 211 (FIG. 1) of Device Aidentifies the current status of power management of Device A (S1). Ifthe power of Device A is in the process of being turned off, CPU 211(FIG. 1) of Device A proceeds to the next step (S2). CPU 211 (FIG. 1) ofDevice A retrieves the 1st power off notice data from 1st Power OffNotice Data Storage Area 206A554 b 4 a (S3). CPU 211 (FIG. 1) of DeviceA outputs the 1st power off notice data retrieved in the previous stepfrom Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device A (S4). CPU 211(FIG. 1) of Device A sends the 1st power off notification to Device B ina wireless fashion (S5). Here, the 1st power off notification indicatesthat Device A is turning off its power. CPU 211 (FIG. 1) of Device Breceives the 1st power off notification from Device A in a wirelessfashion (S6). CPU 211 (FIG. 1) of Device B retrieves the 1st power offnotice data from 1st Power Off Notice Data Storage Area 206B554 b 4 a(S7). CPU 211 (FIG. 1) of Device B outputs the 1st power off notice dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device B (S8). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Power Off Notice Data OutputtingSoftware 206A554 c 4 of Device A and 2nd Power Off Notice DataOutputting Software 206B554 c 4 of Device B, which output(s) the 2ndpower off notice data. In this embodiment, CPU 211 (FIG. 1) of Device Bidentifies the current status of power management of Device B (S1). Ifthe power of Device B is in the process of being turned off, CPU 211(FIG. 1) of Device B proceeds to the next step (S2). CPU 211 (FIG. 1) ofDevice B retrieves the 2nd power off notice data from 2nd Power OffNotice Data Storage Area 206B554 b 4 b (S3). CPU 211 (FIG. 1) of DeviceB outputs the 2nd power off notice data retrieved in the previous stepfrom Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) of Device B (S4). CPU 211(FIG. 1) of Device B sends the 2nd power off notification to Device A ina wireless fashion (S5). Here, the 2nd power off notification indicatesthat Device B is turning off its power. CPU 211 (FIG. 1) of Device Areceives the 2nd power off notification from Device B in a wirelessfashion (S6). CPU 211 (FIG. 1) of Device A retrieves the 2nd power offnotice data from 2nd Power Off Notice Data Storage Area 206A554 b 4 b(S7). CPU 211 (FIG. 1) of Device A outputs the 2nd power off notice dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S8). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 1st Location Data Displaying Software206A554 c 5 of Device A and 1st Location Data Displaying Software206B554 c 5 of Device B, which display(s) the 1st location data. In thisembodiment, CPU 211 (FIG. 1) of Device A identifies the current statusof power management of Device A (S1). If the power of Device A is in theprocess of being turned of CPU 211 (FIG. 1) of Device A proceeds to thenext step (S2). CPU 211 (FIG. 1) of Device A retrieves the map data fromMap Data Storage Area 206A554 b 1 (S3). CPU 211 (FIG. 1) of Device Adisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device A (S4). CPU 211 (FIG. 1) of Device A retrieves the 1stlocation data from 1st Location Data Storage Area 206A554 b 2 a (S5).CPU 211 (FIG. 1) of Device A retrieves the 1st icon image data from 1stIcon Image Data Storage Area 206A554 b 3 a (S6). CPU 211 (FIG. 1) ofDevice A displays the 1st icon image data retrieved in the previous stepat the location corresponding to the 1st location data retrieved in S5on the map data displayed in S4 (S7). CPU 211 (FIG. 1) of Device Aretrieves the 1st location data from 1st Location Data Storage Area206A554 b 2 a and sends the data to Device B in a wireless fashion (S8).CPU 211 (FIG. 1) of Device B receives the 1st location data from DeviceA in a wireless fashion and stores the data in 1st Location Data StorageArea 206B554 b 2 a (S9). CPU 211 (FIG. 1) of Device B retrieves the mapdata from Map Data Storage Area 206B554 b 1 (S10). CPU 211 (FIG. 1) ofDevice B displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device B (S11). CPU 211 (FIG. 1) of Device B retrieves the1st location data from 1st Location Data Storage Area 206B554 b 2 a(S12). CPU 211 (FIG. 1) of Device B retrieves the 1st icon image datafrom 1st Icon Image Data Storage Area 206B554 b 3 a (S13). CPU 211(FIG. 1) of Device B displays the 1st icon image data retrieved in theprevious step at the location corresponding to the 1st location dataretrieved in S12 on the map data displayed in S11 (S14). CPU 211(FIG. 1) of Device B retrieves the 1st location notifying data from 1stLocation Notifying Data Storage Area 206B554 b 5 a (S15). CPU 211(FIG. 1) of Device B outputs the 1st location notifying data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice B (S16). CPU 211 (FIG. 1) of Device B sends the 1st locationnotification to Device A in a wireless fashion (S17). Here, the 1stlocation notification indicates that the current geographic location ofDevice A is displayed on Device B. CPU 211 (FIG. 1) of Device A receivesthe 1st location notification from Device B in a wireless fashion (S18).CPU 211 (FIG. 1) of Device A retrieves the 1st location notifying datafrom 1st Location Notifying Data Storage Area 206A554 b 5 a (S19). CPU211 (FIG. 1) of Device A outputs the 1st location notifying dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device A (S20). The foregoing sequence is repeatedperiodically.

This paragraph illustrate(s) 2nd Location Data Displaying Software206A554 c 6 of Device A and 2nd Location Data Displaying Software206B554 c 6 of Device B, which display(s) the 2nd location data. In thisembodiment, CPU 211 (FIG. 1) of Device B identifies the current statusof power management of Device B (S1). If the power of Device B is in theprocess of being turned of CPU 211 (FIG. 1) of Device B proceeds to thenext step (S2). CPU 211 (FIG. 1) of Device B retrieves the map data fromMap Data Storage Area 206B554 b 1 (S3). CPU 211 (FIG. 1) of Device Bdisplays the map data retrieved in the previous step on LCD 201 (FIG. 1)of Device B (S4). CPU 211 (FIG. 1) of Device B retrieves the 2ndlocation data from 2nd Location Data Storage Area 206B554 b 2 b (S5).CPU 211 (FIG. 1) of Device B retrieves the 2nd icon image data from 2ndIcon Image Data Storage Area 206B554 b 3 b (S6). CPU 211 (FIG. 1) ofDevice B displays the 2nd icon image data retrieved in the previous stepat the location corresponding to the 2nd location data retrieved in S5on the map data displayed in S4 (S7). CPU 211 (FIG. 1) of Device Bretrieves the 2nd location data from 2nd Location Data Storage Area206B554 b 2 b and sends the data to Device A in a wireless fashion (S8).CPU 211 (FIG. 1) of Device A receives the 2nd location data from DeviceB in a wireless fashion and stores the data in 2nd Location Data StorageArea 206A554 b 2 b (S9). CPU 211 (FIG. 1) of Device A retrieves the mapdata from Map Data Storage Area 206A554 b 1 (S10). CPU 211 (FIG. 1) ofDevice A displays the map data retrieved in the previous step on LCD 201(FIG. 1) of Device A (S11). CPU 211 (FIG. 1) of Device A retrieves the2nd location data from 2nd Location Data Storage Area 206A554 b 2 b(S12). CPU 211 (FIG. 1) of Device A retrieves the 2nd icon image datafrom 2nd Icon Image Data Storage Area 206A554 b 3 b (S13). CPU 211(FIG. 1) of Device A displays the 2nd icon image data retrieved in theprevious step at the location corresponding to the 2nd location dataretrieved in S12 on the map data displayed in S11 (S14). CPU 211(FIG. 1) of Device A retrieves the 2nd location notifying data from 2ndLocation Notifying Data Storage Area 206A554 b 5 b (S15). CPU 211(FIG. 1) of Device A outputs the 2nd location notifying data retrievedin the previous step from Speaker 216 (FIG. 1) and LCD 201 (FIG. 1) ofDevice A (S16). CPU 211 (FIG. 1) of Device A sends the 2nd locationnotification to Device B in a wireless fashion (S17). Here, the 2ndlocation notification indicates that the current geographic location ofDevice B is displayed on Device A. CPU 211 (FIG. 1) of Device B receivesthe 2nd location notification from Device A in a wireless fashion (S18).CPU 211 (FIG. 1) of Device B retrieves the 2nd location notifying datafrom 2nd Location Notifying Data Storage Area 206B554 b 5 b (S19). CPU211 (FIG. 1) of Device B outputs the 2nd location notifying dataretrieved in the previous step from Speaker 216 (FIG. 1) and LCD 201(FIG. 1) of Device B (S20). The foregoing sequence is repeatedperiodically.

<<Multiple Mode Implementing Function>>

The following paragraphs illustrate the multiple mode implementingfunction of Communication Device 200 which enables to activate andimplement a plurality of modes, functions, and/or systems described inthis specification simultaneously.

This paragraph illustrates the software programs stored in RAM 206(FIG. 1) to implement the multiple mode implementing function (FIG. 1).In this embodiment, RAM 206 includes Multiple Mode Implementer StorageArea 20690 a. Multiple Mode Implementer Storage Area 20690 a storesMultiple Mode Implementer 20690 b, Mode List Displaying Software 20690c, Mode Selecting Software 20690 d, Mode Activating Software 20690 e,and Mode Implementation Repeater 20690 f, all of which are softwareprograms. Multiple Mode Implementer 20690 b administers the overallimplementation of the present function. One of the major tasks ofMultiple Mode Implementer 20690 b is to administer and control thetiming and sequence of Mode List Displaying Software 20690 c, ModeSelecting Software 20690 d, Mode Activating Software 20690 e, and ModeImplementation Repeater 20690 f. For example, Multiple Mode Implementer20690 b executes them in the following order: Mode List DisplayingSoftware 20690 c, Mode Selecting Software 20690 d, Mode ActivatingSoftware 20690 e, and Mode Implementation Repeater 20690 f. Mode ListDisplaying Software 20690 c displays on LCD 201 (FIG. 1) a list of acertain amount or all modes, functions, and/or systems explained in thisspecification of which the sequence is explained hereinafter. ModeSelecting Software 20690 d selects a certain amount or all modes,functions, and/or systems explained in this specification of which thesequence is explained hereinafter. Mode Activating Software 20690 eactivates a certain amount or all modes, functions, and/or systemsselected by the Mode Selecting Software 20690 d of which the sequence isexplained hereinafter. Mode Implementation Repeater 20690 f executesMultiple Mode Implementer 20690 b which reactivates Mode List DisplayingSoftware 20690 c, Mode Selecting Software 20690 d, Mode ActivatingSoftware 20690 e of which the sequence is explained hereinafter.

This paragraph illustrates the sequence of Mode List Displaying Software20690 c. In this embodiment, CPU 211 (FIG. 1), under the command of ModeList Displaying Software 20690 c, displays a list of a certain amount orall modes, functions, and/or systems described in this specification onLCD 201 (FIG. 1).

This paragraph illustrates the sequence of Mode Selecting Software 20690d. In this embodiment, the user of Communication Device 200 inputs aninput signal by utilizing Input Device 210 (FIG. 1) or via voicerecognition system identifying one of the modes, functions, and/orsystems displayed on LCD 201 (FIG. 1) (S1), and CPU 211 (FIG. 1), underthe command of Mode Selecting Software 20690 d, interprets the inputsignal and selects the corresponding mode, function, or system (S2).

This paragraph illustrates the sequence of Mode Activating Software20690 e. In this embodiment, CPU 211 (FIG. 1), under the command of ModeActivating Software 20690 e, activates the mode, function, or, systemselected in S2 described in the previous paragraph. CPU 211 thereafterimplements the activated mode, function, or system as described in therelevant paragraphs in this specification.

This paragraph illustrates the sequence of Mode Implementation Repeater20690 f. In this embodiment, the user of Communication Device 200 inputsan input signal by utilizing Input Device 210 (FIG. 1) or via voicerecognition system (S1). Once the activation of the selected mode,function, or system described hereinbefore is completed, and if theinput signal indicates to repeat the process to activate another mode,function, or system (S2), CPU 211 (FIG. 1), under the command of ModeImplementation Repeater 20690 f, executes Multiple Mode Implementer20690 b, which reactivates Mode List Displaying Software 20690 c, ModeSelecting Software 20690 d, and Mode Activating Software 20690 e toactivate the second mode, function, or system while the first mode,function, or system is implemented by utilizing the method of so-called‘time sharing’ (S3). Mode List Displaying Software 20690 c, ModeSelecting Software 20690 d, and Mode Activating Software 20690 e can berepeatedly executed until all modes, function, and systems displayed onLCD 201 (FIG. 1) are selected and activated. The activation of modes,functions, and/or systems is not repeated if the input signal explainedin S2 so indicates.

As another embodiment, Multiple Mode Implementer 20690 b, Mode ListDisplaying Software 20690 c, Mode Selecting Software 20690 d, ModeActivating Software 20690 e, and Mode Implementation Repeater 20690 fdescribed hereinbefore may be integrated into one software program,Multiple Mode Implementer 20690 b. In this embodiment, CPU 211 (FIG. 1),first of all, displays a list of a certain amount or all modes,functions, and/or systems described in this specification on LCD 201(FIG. 1) (S1). Next, the user of Communication Device 200 inputs aninput signal by utilizing Input Device 210 (FIG. 1) or via voicerecognition system identifying one of the modes, functions, and/orsystems displayed on LCD 201 (S2), and CPU 211 interprets the inputsignal and selects the corresponding mode, function, or system (S3). CPU211 activates the mode, function, or system selected in S3, andthereafter implements the activated mode, function, or system asdescribed in the relevant paragraphs in this specification (S4). Oncethe activation of the selected mode, function, or system described in S4is completed, the user of Communication Device 200 inputs an inputsignal by utilizing Input Device 210 or via voice recognition system(S5). If the input signal indicates to repeat the process to activateanother mode, function, or system (S6), CPU 211 repeats the steps S1through S4 to activate the second mode, function, or system while thefirst mode, function, or system is implemented by utilizing the methodso-called ‘time sharing’. The steps of S1 though S4 can be repeatedlyexecuted until all modes, function, and systems displayed on LCD 201 areselected and activated. The activation of modes, functions, and/orsystems is not repeated if the input signal explained in S5 soindicates. As another embodiment, before or at the time one softwareprogram is activated, CPU 211 may, either automatically or manually(i.e., by a signal input by the user of Communication Device), terminatethe other software programs already activated or prohibit other softwareprograms to be activated while one software program is implemented inorder to save the limited space of RAM 206, thereby allowing only onesoftware program implemented at a time. For the avoidance of doubt, themeaning of each term ‘mode(s)’, ‘function(s)’, and ‘system(s)’ isequivalent to the others in this specification. Namely, the meaning of‘mode(s)’ includes and is equivalent to that of ‘function(s)’ and‘system(s)’, the meaning of ‘function(s)’ includes and is equivalent tothat of ‘mode(s)’ and ‘system(s)’, and the meaning of ‘system(s)’includes and is equivalent to that of ‘mode(s)’ and ‘function(s)’.Therefore, even only mode(s) is expressly utilized in thisspecification, it impliedly includes function(s) and/or system(s) by itsdefinition.

<<Incorporation By Reference>>

The following paragraphs and drawings described in U.S. Ser. No.11/423,432 filed 2006-06-10 are incorporated to this application byreference: the preamble described in paragraph [2149] (no drawings);Communication Device 200 (Voice Communication Mode) described inparagraphs [2150] through [2155] (FIGS. 1 through 2 c); VoiceRecognition System described in paragraphs [2156] through [2188] (FIGS.3 through 19); Positioning System described in paragraphs [2189] through[2220] (FIGS. 20 a through 32 e); Auto Backup System described inparagraphs [2221] through [2230] (FIGS. 33 through 37); Signal Amplifierdescribed in paragraphs [2231] through [2236] (FIG. 38); Audio/VideoData Capturing System described in paragraphs [2237] through [2249](FIGS. 39 through 44 b); Digital Mirror Function (1) described inparagraphs [2250] through [2258] (FIGS. 44 c through 44 e); Caller IDSystem described in paragraphs [2259] through [2266] (FIGS. 45 through47); Stock Purchasing Function described in paragraphs [2267] through[2276] (FIGS. 48 through 52); Timer Email Function described inparagraphs [2277] through [2283] (FIGS. 53 a and 53 b); Call BlockingFunction described in paragraphs [2284] through [2297] (FIGS. 54 through59); Online Payment Function described in paragraphs [2298] through[2307] (FIGS. 60 through 64); Navigation System described in paragraphs[2308] through [2330] (FIGS. 65 through 74 a); Remote Controlling Systemdescribed in paragraphs [2331] through [2349] (FIGS. 75 through 85);Auto Emergency Calling System described in paragraphs [2350] through[2358] (FIGS. 86 and 87); Cellular TV Function described in paragraphs[2359] through [2443] (FIGS. 88 through 135); 3D Video Game Functiondescribed in paragraphs [2444] through [2456] (FIGS. 136 through 144);Digital Mirror Function (2) described in paragraphs [2457] through[2466] (FIGS. 145 through 155); Voice Recognition Sys-E-mail (2)described in paragraphs [2467] through [2475] (FIGS. 156 through 160);Positioning System—GPS Search Engine described in paragraphs [2476]through [2518] (FIGS. 161 through 182); Mobile Ignition Key Functiondescribed in paragraphs [2519] through [2541] (FIGS. 183 through 201);Voice Print Authentication System described in paragraphs [2542] through[2552] (FIGS. 202 through 211); Fingerprint Authentication Systemdescribed in paragraphs [2553] through [2565] (FIGS. 212 through 221);Auto Time Adjust Function described in paragraphs [2566] through [2570](FIGS. 222 through 224); Video/Photo Mode described in paragraphs [2571]through [2599] (FIGS. 225 through 242); Call Taxi Function described inparagraphs [2600] through [2640] (FIGS. 243 through 269); Shooting VideoGame Function described in paragraphs [2641] through [2657] (FIGS. 270through 283); Driving Video Game Function described in paragraphs [2658]through [2671] (FIGS. 284 through 294); Address Book Updating Functiondescribed in paragraphs [2672] through [2692] (FIGS. 295 through 312);Batch Address Book Updating Function—With Host described in paragraphs[2693] through [2714] (FIGS. 313 through 329); Batch Address BookUpdating Function—Peer-To-Peer Connection described in paragraphs [2715]through [2719] (FIGS. 329 a through 329 c); Batch Scheduler UpdatingFunction—With Host described in paragraphs [2720] through [2743] (FIGS.330 through 350); Batch Scheduler Updating Function—Peer-To-PeerConnection described in paragraphs [2744] through [2748] (FIGS. 351 and352); Calculator Function described in paragraphs [2749] through [2754](FIGS. 353 through 356); Spreadsheet Function described in paragraphs[2755] through [2762] (FIGS. 357 through 360); Word Processing Functiondescribed in paragraphs [2763] through [2778] (FIGS. 361 through 373);TV Remote Controller Function described in paragraphs [2779] through[2801] (FIGS. 374 through 394); CD/PC Inter-communicating Functiondescribed in paragraphs [2802] through [2826] (FIGS. 413 through 427);PDWR Sound Selecting Function described in paragraphs [2827] through[2863] (FIGS. 428 through 456); Start Up Software Function described inparagraphs [2864] through [2880] (FIGS. 457 through 466); AnotherEmbodiment Of Communication Device 200 described in paragraphs [2881]through [2885] (FIGS. 467 a through 467 d); Stereo Audio Data OutputFunction described in paragraphs [2886] through [2905] (FIGS. 468through 479); Stereo Visual Data Output Function described in paragraphs[2906] through [2925] (FIGS. 480 through 491); Multiple SignalProcessing Function described in paragraphs [2926] through [2998] (FIGS.492 through 529); Positioning System—Pin-pointing Function described inparagraphs [2999] through [3032] (FIGS. 530 through 553); ArtificialSatellite Host described in paragraphs [3033] through [3051] (FIGS. 554through 567); CCD Bar Code Reader Function described in paragraphs[3052] through [3073] (FIGS. 568 through 579); Online Renting Functiondescribed in paragraphs [3074] through [3151] (FIGS. 580 through 633);SOS Calling Function described in paragraphs [3152] through [3172](FIGS. 634 through 645); Input Device described in paragraphs [3173]through [3178] (FIGS. 646 through 650); PC Remote Controlling Functiondescribed in paragraphs [3179] through [3214] (FIGS. 651 through 670);PC Remote Downloading Function described in paragraphs [3215] through[3264] (FIGS. 671 through 701); Audiovisual Playback Function describedin paragraphs [3265] through [3290] (FIGS. 702 through 716); AudioPlayback Function described in paragraphs [3291] through [3315] (FIGS.717 through 731); Ticket Purchasing Function described in paragraphs[3316] through [3345] (FIGS. 732 through 753); Remote Data ErasingFunction described in paragraphs [3346] through [3375] (FIGS. 754through 774); Business Card Function described in paragraphs [3376]through [3392] (FIGS. 775 through 783); Game Vibrating Functiondescribed in paragraphs [3393] through [3403] (FIGS. 784 through 786);Part-time Job Finding Function described in paragraphs [3404] through[3424] (FIGS. 787 through 801); Parking Lot Finding Function describedin paragraphs [3425] through [3464] (FIGS. 802 through 832); PartsUpgradable Communication Device described in paragraphs [3465] through[3490] (FIGS. 833 a through 833 x); On Demand TV Function described inparagraphs [3491] through [3521] (FIGS. 834 through 855);Inter-communicating TV Function described in paragraphs [3522] through[3556] (FIGS. 856 through 882); Display Controlling Function describedin paragraphs [3557] through [3574] (FIGS. 883 through 894); MultipleParty Communicating Function described in paragraphs [3575] through[3608] (FIGS. 894 a through 917); Display Brightness ControllingFunction described in paragraphs [3609] through [3618] (FIGS. 918through 923); Multiple Party Pin-pointing Function described inparagraphs [3619] through [3666] (FIGS. 924 through 950 f); DigitalCamera Function described in paragraphs [3667] through [3694] (FIGS. 951through 968); Phone Number Linking Function described in paragraphs[3695] through [3718] (FIGS. 968 a through 983); Multiple WindowDisplaying Function described in paragraphs [3719] through [3737] (FIGS.984 through 995); Mouse Pointer Displaying Function described inparagraphs [3738] through [3775] (FIGS. 996 through 1021); House ItemPin-pointing Function described in paragraphs [3776] through [3935](FIGS. 1022 through 1152); Membership Administrating Function describedin paragraphs [3936] through [3978] (FIGS. 1153 through 1188); KeywordSearch Timer Recording Function described in paragraphs [3979] through[4070] (FIGS. 1189 through 1254); Weather Forecast Displaying Functiondescribed in paragraphs [4071] through [4112] (FIGS. 1255 through 1288);Multiple Language Displaying Function described in paragraphs [4113]through [4170] (FIGS. 1289 through 1331); Caller's InformationDisplaying Function described in paragraphs [4171] through [4224] (FIGS.1332 through 1375); Communication Device Remote Controlling Function (ByPhone) described in paragraphs [4225] through [4265] (FIGS. 1394 through1415); Communication Device Remote Controlling Function (By Web)described in paragraphs [4266] through [4306] (FIGS. 1416 through 1437);Shortcut Icon Displaying Function described in paragraphs [4307] through[4334] (FIGS. 1438 through 1455); Task Tray Icon Displaying Functiondescribed in paragraphs [4335] through [4357] (FIGS. 1456 through 1470);Multiple Channel Processing Function described in paragraphs [4358]through [4405] (FIGS. 1471 through 1498); Solar Battery ChargingFunction described in paragraphs [4406] through [4419] (FIGS. 1499through 1509); OS Updating Function described in paragraphs [4420]through [4487] (FIGS. 1510 through 1575); Device Managing Functiondescribed in paragraphs [4488] through [4505] (FIGS. 1576 through 1587);Automobile Controlling Function described in paragraphs [4506] through[4554] (FIGS. 1588 through 1627); OCR Function described in paragraphs[4555] through [4590] (FIGS. 1628 through 1652); Real-time GPS Functiondescribed in paragraphs [4591] through [4660] (FIGS. 1653 through 1712);CCD Video Stabilizing Function described in paragraphs [4661] through[4692] (FIGS. 1713 through 1736); DVD Remote Controlling Functiondescribed in paragraphs [4693] through [4731] (FIGS. 1737 through 1757);Dual Frame Buffer Implementing Function described in paragraphs [4732]through [4748] (FIGS. 1758 through 1767); Mouse Pointer Image AutoChanging Function described in paragraphs [4749] through [4762] (FIGS.1768 through 1774); Dual CCD Camera Function described in paragraphs[4763] through [4783] (FIGS. 1775 a through 1786); Radio Tuner Functiondescribed in paragraphs [4784] through [4814] (FIGS. 1787 through 1812);Registered Voice Recognizing Function described in paragraphs [4815]through [4854] (FIGS. 1813 through 1842); Host's TV ResolutionConverting Function described in paragraphs [4855] through [4884] (FIGS.1843 through 1864); Voice Shortcut Recognizing Function described inparagraphs [4885] through [4919] (FIGS. 1865 through 1889); Vital SignMonitoring Function described in paragraphs [4920] through [5009] (FIGS.1890 a through 1954); Three-Dimensional Map described in (FIGS. 2 and3); Auto Collision Avoiding Function described in (FIGS. 4 through 7);Remote Controlling System described in (FIGS. 8 a through FIG. 10);Emergency Landing System described in (FIGS. 11 through FIG. 12 b);Connection Between Host H And Carrier 300 described in (FIG. 13); 3D MapData Updating Function described in (FIGS. 16 through 30); AutoCollision Avoiding Function—Other Embodiments described in (FIGS. 31through 34); Satellite TV Function described in (FIGS. 35 through 50);Wireless Communication Facilitating System described in (FIGS. 51through 64 b); Three-Dimensional Map described in (??); Attached FileEmailing Function described in paragraphs [5009.1] through [5009.13](FIGS. 1955 through 1961); Movie eTicket Function described inparagraphs [5009.14] through [5009.66] (FIGS. 1962 through 2002);Carrier Prepaid eCard Function described in paragraphs [5009.67] through[5009.104] (FIGS. 2003 through 2032); Carrier ePass Function describedin paragraphs [5009.105] through [5009.144] (FIGS. 2033 through 2061 b);Communication Device 200 Installed In Carrier described in paragraphs[5009.145] and [5009.146] (FIG. 2062); Wireless CommunicationFacilitating System described in paragraphs [5009.147] through[5009.176] (FIGS. 2063 through 2076 b); In-Carrier Notifying Functiondescribed in paragraphs [5009.177] through [5009.207] (FIGS. 2077through 2093); Station Name Notifying Function described in paragraphs[5009.208] through [5009.237] (FIGS. 2094 through 2110); RestauranteMenu Function described in paragraphs [5009.238] through [5009.280](FIGS. 2111 through 2144); Geographic Location Recording Functiondescribed in paragraphs [5009.281] through [5009.322] (FIGS. 2145through 2176 b); CCD Dictionary Function described in paragraphs[5009.323] through [5009.347] (FIGS. 2177 through 2195 b); ScheduleNotifying Function described in paragraphs [5009.348] through [5009.374](FIGS. 2196 through 2215); Customized Device Purchasing System describedin paragraphs [5009.375] through [5009.415] (FIGS. 2216 through 2250);Multiple Type TV Program Distributing System described in paragraphs[5009.416] through [5009A46] (FIGS. 2251 through 2274); Multiple TVScreen Displaying Function described in paragraphs [5009.447] through[5009.478] (FIGS. 2275 through 2297); Touch Panel Function described inparagraphs [5009.479] through [5009.504] (FIGS. 2298 through 2315);Communication Device Finding Function described in paragraphs [5009.505]through [5009.516] (FIGS. 2316 through 2322); Carrier Safety MeasureControlling Function described in paragraphs [5009.517] through[5009.551] (FIGS. 2323 through 2342); Product Information RetrievingFunction (CCD) described in paragraphs [5009.552] through [5009.580](FIGS. 2343 through 2360); Product Information Stored Chip Functiondescribed in paragraphs [5009.581] through [5009.618] (FIGS. 2361through 2385); Karaoke Playing Function described in paragraphs[5009.619] through [5009.647] (FIGS. 2386 through 2406); PerformingPattern Identifying Anti-Virus Function described in paragraphs[5009.648] through [5009.670] (FIGS. 2407 through 2421); ContinueEnabled Video Game Function described in paragraphs [5009.671] through[5009.693] (FIGS. 2422 through 2436); Resume Enabled Video Game Functiondescribed in paragraphs [5009.694] through [5009.716] (FIGS. 2437through 2451); Signal Forwarding Function described in paragraphs[5009.717] through [5009.745] (FIGS. 2452 through 2472); In-Carrier AutoImplementing Mode Function described in paragraphs [5009.746] through[5009.775] (FIGS. 2473 through 2492); Voice Message Displaying Functiondescribed in paragraphs [5009.776] through [5009.796] (FIGS. 2493through 2503 c); Human Toes Displaying Function described in paragraphs[5009.797] through [5009.814] (FIGS. 2504 through 2521);Wrinkles/Muscles Displaying Function described in paragraphs [5009.815]through [5009.856] (FIGS. 2522 a through 2552 e); Protruded Body PartDisplaying Function described in paragraphs [5009.857] through[5009.876] (FIGS. 2553 through 2566 b); Satellite TV Program DisplayingFunction described in paragraphs [5009.877] through [5009.921] (FIGS.2567 through 2601); Definition of Communication Device 200 described inparagraphs [5009.922] and [5009.923] (no drawings); Remote ParameterSetting Function described in paragraphs [5009.924] through [5009.1017](FIGS. 2602 through 2682); Multiple Sender's Email Address Functiondescribed in paragraphs [5009.1018] through [5009.1035] (FIGS. 2683through 2695); Multiple Phone Number Function described in paragraphs[5009.1036] through [5009.1055] (FIGS. 2696 through 2709); TV CommercialCustomizing Function described in paragraphs [5009.1056] through[5009.1085] (FIGS. 2710 through 2732 c); Common Video Game PlatformFunction described in paragraphs [5009.1086] through [5009.1102] (FIGS.2733 through 2741); Directory Displaying Function described inparagraphs [5009.1103] through [5009.1130] (FIGS. 2742 through 2761);Directory Customizing Function described in paragraphs [5009.1131]through [5009.1186] (FIGS. 2762 through 2807); Host's DirectoryCustomizing Function described in paragraphs [5009.1187] through[5009.1246] (FIGS. 2808 through 2853); Trash Can Function described inparagraphs [5009.1247] through [5009.1295] (FIGS. 2854 through 28950;Motion Character Displaying Function described in paragraphs [5009.1296]through [5009.1318] (FIGS. 2896 through 2909); Bookmark DisplayingFunction described in paragraphs [5009.1319] through [5009.1374] (FIGS.2910 through 2955); CCD/LCD Function described in paragraphs [5009.1375]through [5009.1387] (FIGS. 2956 through 2959 b); Pop Up Window BlockingFunction described in paragraphs [5009.1388] through [5009.1401] (FIGS.2960 through 2965); Map Heading Up Function described in paragraphs[5009.1402] through [5009.1421] (FIGS. 2966 through 2976); Copy OnceFunction described in paragraphs [5009.1422] through [5009.1443] (FIGS.2977 through 2991); Copy Restricted Software Integrated Data describedin paragraphs [5009.1444] through [5009.1457] (FIGS. 2992 through 2998);Folder Sharing Function described in paragraphs [5009.1458] through[5009.1508] (FIGS. 2999 through 3038 c); Email Folder Managing Functiondescribed in paragraphs [5009.1509] through [5009.1577] (FIGS. 3039through 3092 e); Power On Auto Software Executing Function described inparagraphs [5009.1578] through [5009.1594] (FIGS. 3093 through 3103);Enhanced TV Remote Controlling Function described in paragraphs[5009.1595] through [5009.1639] (FIGS. 3104 through 3137 c); 3 CCD UnitFunction described in paragraphs [5009.1640] through [5009.1660] (FIGS.3138 through 3150 c); Multiple Direction Scrolling Function described inparagraphs [5009.1661] through [5009.1762] (FIGS. 3151 through 3238);Radio Frequency Soft Handover Function described in paragraphs[5009.1763] through [5009.1793] (FIGS. 3239 through 3262); Inter ComFunction described in paragraphs [5009.1794] through [5009.1816] (FIGS.3263 through 3277 c); Website History Recording Function described inparagraphs [5009.1817] through [5009.1870] (FIGS. 3278 through 3324);Motion Picture Thumbnail Displaying Function described in paragraphs[5009.1871] through [5009.1908] (FIGS. 3325 through 3353 b); 2D/3D MapDisplaying Function described in paragraphs [5009.1909] through[5009.1952] (FIGS. 3354 through 3380 b); Remote Schedule NotifyingFunction described in paragraphs [5009.1953] through [5009.1975] (FIGS.3381 through 3393); Remote Email Notifying Function described inparagraphs [5009.1976] through [5009.2000] (FIGS. 3394 through 3406);Remote Document Printing Function described in paragraphs [5009.2001]through [5009.2022] (FIGS. 3407 through 3419 b); Anti-virus ProtectionIdentifying Function described in paragraphs [5009.2023] through[5009.2043] (FIGS. 3420 through 3431 c); Alphanumeric Phone NumberDialing Function described in paragraphs [5009.2044] through [5009.2076](FIGS. 3432 through 3453 b); Automobile License Number Dialing Functiondescribed in paragraphs [5009.2077] through [5009.2109] (FIGS. 3454through 3475 b); Point Card Function described in paragraphs [50092110]through [5009.2147] (FIGS. 3476 through 3504 c); Display SharingFunction described in paragraphs [5009.2148] through [5009.2169] (FIGS.3505 through 3516); Email Filtering Function described in paragraphs[5009.2170] through [5009.2212] (FIGS. 3517 through 3549); ReceivedEmail Auto Sorting Function described in paragraphs [5009.2213] through[5009.2238] (FIGS. 3550 through 3565 b); Sent Email Auto SortingFunction described in paragraphs [5009.2239] through [5009.2264] (FIGS.3566 through 3581 b); Country Name Displaying Function described inparagraphs [5009.2265] through [5009.2286] (FIGS. 3582 through 3595);Email Attached File Splitting Function described in paragraphs[5009.2287] through [5009.2300] (FIGS. 3596 through 3603 c); Auto TVStarting Function described in paragraphs [5009.2301] through[5009.2329] (FIGS. 3604 through 3623); Enhanced TV Program ReplayingFunction (Communication Device 200) described in paragraphs [5009.2330]through [5009.2361] (FIGS. 3624 through 3648 b); Enhanced TV ProgramReplaying Function (Host H) described in paragraphs [5009.2362] through[5009.2400] (FIGS. 3649 through 3680 b); Enhanced TV Program ReplayingFunction (Devices A and B) described in paragraphs [5009.2401] through[5009.2440] (FIGS. 3681 through 3712 b); Enhanced TV Program ReplayingFunction (Host H, and Devices A and B) described in paragraphs[5009.2441] through [5009.2491] (FIGS. 3713 through 3754 b); TVCommercial Skipping Function described in paragraphs [5009.2492] through[5009.2516] (FIGS. 3755 through 3772); Timer Schedule Auto ChangingFunction described in paragraphs [5009.2517] through [5009.2542] (FIGS.3773 through 3789); Remote Alarm Setting Function described inparagraphs [5009.2543] through [5009.2585] (FIGS. 3789 a through 3817b); Current Location Non-notifying Function described in paragraphs[5009.2586] through [5009.2612] (FIGS. 3818 through 3833); DeviceRemotely Locking Function described in paragraphs [5009.2613] through[5009.2644] (FIGS. 3834 through 3857); EZ Macro Function described inparagraphs [5009.2645] through [5009.2668] (FIGS. 3858 through 3873 b);Alcohol Level Identifying Function described in paragraphs [5009.2669]through [5009.2694] (FIGS. 3874 through 3889 b); Displayed Visual DataSize Modifying Function described in paragraphs [5009.2695] through[5009.2729] (FIGS. 3890 through 3915); Button Size Changing Functiondescribed in paragraphs [5009.2730] through [5009.2758] (FIGS. 3916through 3937); Epayment Sound Selecting Function described in paragraphs[5009.2759] through [5009.2778] (FIGS. 3938 through 3950 c); Multiple TVProgram Recording Function described in paragraphs [5009.2779] through[5009.2823] (FIGS. 3951 through 3988); TV Program Data Trashcan Functiondescribed in paragraphs [5009.2824] through [5009.2856] (FIGS. 3989through 4010 b); Ereceipt Producing Function described in paragraphs[5009.2857] through [5009.2888] (FIGS. 4011 through 4033); Memo SharingFunction described in paragraphs [5009.2889] through [5009.2930] (FIGS.4034 through 4064); Selected Function Remotely Freezing Functiondescribed in paragraphs [5009.2931] through [5009.2964] (FIGS. 4065through 4085); Selected Software Remotely Activating Function describedin paragraphs [5009.2965] through [5009.2998] (FIGS. 4086 through 4106);Selected Function Remotely Activating Function described in paragraphs[5009.2999] through [5009.3032] (FIGS. 4107 through 4127); SelectedSoftware Remotely Freezing Function described in paragraphs [5009.3033]through [5009.3066] (FIGS. 4128 through 4148); Selected Data RemotelyDeleting Function described in paragraphs [5009.3067] through[5009.3100] (FIGS. 4149 through 4169); Web Cash Memory Functiondescribed in paragraphs [5009.3101] through [5009.3122] (FIGS. 4170through 4183 b); Keypad Auto Unlocking Function described in paragraphs[5009.3123] through [5009.3145] (FIGS. 4184 through 4199); Voice RecogSys Auto Unlocking Function described in paragraphs [5009.3146] through[5009.3168] (FIGS. 4200 through 4215); Upgraded Voice Recog Sys AutoUnlocking Function described in paragraphs [5009.3169] through[5009.3192] (FIGS. 4216 through 4231); TV Program Information DisplayingFunction described in paragraphs [5009.3193] through [5009.3215] (FIGS.4232 through 4247 b); Best Signal Auto Selecting Function described inparagraphs [5009.3216] through [5009.3269] (FIGS. 4248 through 4291);Software Timer Activating Function described in paragraphs [5009.3270]through [5009.3295] (FIGS. 4292 through 4305 b); Software TimerTerminating Function described in paragraphs [5009.3296] through[5009.3321] (FIGS. 4306 through 4319 b); Software Timer DeletingFunction described in paragraphs [5009.3322] through [5009.3347] (FIGS.4320 through 4333 b); TV Phone Recording Function described inparagraphs [5009.3348] through [5009.3381] (FIGS. 4334 through 4358 b);Hybrid GPS Function described in paragraphs [5009.3382] through[5009.3421] (FIGS. 4359 through 4381); Elevator Controlling Functiondescribed in paragraphs [5009.3422] through [5009.3447] (FIGS. 4382through 4397); Device Migrating Function described in paragraphs[5009.3448] through [5009.3509] (FIGS. 4398 through 4445 b); CordlessPhone Connecting Function described in paragraphs [5009.3510] through[5009.3547] (FIGS. 4446 through 4474 b); Cash Deposit Function describedin paragraphs [5009.3548] through [5009.3585] (FIGS. 4475 through 4497d); Highway Fee Auto Paying Function described in paragraphs [5009.3586]through [5009.3616] (FIGS. 4498 through 4518 f); By Distance Auto ActionFunction described in paragraphs [5009.3617] through [5009.3639] (FIGS.4519 through 4532); Emoney Transferring Function described in paragraphs[5009.3640] through [5009.3666] (FIGS. 4533 through 4548 c); CouponDisposing Function described in paragraphs [5009.3667] through[5009.3698] (FIGS. 4549 through 4569); Multiple Device SearchingFunction described in paragraphs [5009.3699] through [5009.3717] (FIGS.4570 through 4581 b); Battery Meter Notifying Function described inparagraphs [5009.3718] through [5009.3737] (FIGS. 4582 through 4593 b);Software Infrared Transmitting Function described in paragraphs[5009.3738] through [5009.3759] (FIGS. 4594 through 4606); ElectronicKey Function described in paragraphs [5009.3760] through [5009.3824](FIGS. 4607 through 4647 b); Automobile Status Monitoring Functiondescribed in paragraphs [5009.3825] through [5009.3885] (FIGS. 4648through 4691); Enhanced Business Card Transferring Function described inparagraphs [5009.3886] through [5009.3928] (FIGS. 4692 through 4720 c);Removal Media Data Transferring Function described in paragraphs[5009.3929] through [5009.3954] (FIGS. 4721 through 4737 c); AudiovisualData Sharing Function described in paragraphs [5009.3955] through[5009.3992] (FIGS. 4738 through 4763 b); Email Attachment SupplementingFunction described in paragraphs [5009.3993] through [5009.4012] (FIGS.4764 through 4775 c); Other Device File Emailing Function described inparagraphs [5009.4013] through [5009.4043] (FIGS. 4776 through 4799 b);Slide Authoring Function described in paragraphs [5009.4044] through[5009.4082] (FIGS. 4800 through 4828); Remote/Local Credit CardTransaction Function described in paragraphs [5009.4083] through[5009.4119] (FIGS. 4829 through 4855 d); Unread Email Sorting Functiondescribed in paragraphs [5009.4120] through [5009.4166] (FIGS. 4856through 4890); TV Program Replying Function described in paragraphs[5009.4167] through [5009.4200] (FIGS. 4891 through 4914); PC KeyboardFunction described in paragraphs [5009.4201] through [5009.4212] (FIGS.4915 through 4920 b); Antenna Mark Displaying Function described inparagraphs [5009.4213] through [5009.4228] (FIGS. 4921 through 4928 b);Enhanced Caller ID Displaying Function described in paragraphs[5009.4229] through [5009.4264] (FIGS. 4929 through 4951 c); EnhancedCall Waiting Function described in paragraphs [5009.4265] through[5009.4300] (FIGS. 4952 through 4974 c); Phonebook Auto Icon DisplayingFunction described in paragraphs [5009.4301] through [5009.4332] (FIGS.4975 through 4996); One Click Call Back Function described in paragraphs[5009.4333] through [5009.4357] (FIGS. 4997 through 5014); PhoneConversation Storing Function described in paragraphs [5009.4358]through [5009.4386] (FIGS. 5015 through 5031 c); Caller ID RequestingFunction described in paragraphs [5009.4387] through [5009.4410] (FIGS.5032 through 5045 c); Phone Call Audio Notifying Function described inparagraphs [5009.4411] through [5009.4433] (FIGS. 5046 through 5059 c);Entry Phone Function described in paragraphs [5009.4434] through[5009.4459] (FIGS. 5060 through 5074 b); FAX Sending/Receiving Functiondescribed in paragraphs [5009.4460] through [5009.4505] (FIGS. 5075through 5108 b); Other Device's Phone Book Utilizing Function describedin paragraphs [5009.4506] through [5009.4536] (FIGS. 5109 through 5128);Multiple Program Executing Function described in paragraphs [5009.4537]through [5009.4564] (FIGS. 5129 through 5148); Removal Medium OperatingFunction described in paragraphs [5009.4565] through [5009.4601] (FIGS.5149 through 5178); Removal Medium Audiovisual Data Recording Functiondescribed in paragraphs [5009.4602] through [5009.4629] (FIGS. 5178 athrough 5199); Nearest Printer Selecting Function described inparagraphs [5009.4630] through [5009.4656] (FIGS. 5200 through 5216 d);In-Cabin Com Function described in paragraphs [5009.4657] through[5009.4680] (FIGS. 5217 through 5233 c); Carrier Current ConditionNotifying Function described in paragraphs [5009.4681] through[5009.4710] (FIGS. 5234 through 5251 b); Virtual Space Creating Functiondescribed in paragraphs [5009.4711] through [5009.4743] (FIGS. 5252through 5274); Security Camera Function described in paragraphs[5009.4744] through [5009.4778] (FIGS. 5275 through 5295); Remote CameraControlling Function described in paragraphs [5009.4779] through[5009.4820] (FIGS. 5296 through 5326); Day/Night Camera Functiondescribed in paragraphs [5009.4821] through [5009.4851] (FIGS. 5327through 5346); Multiple Wireless Signal Handover Function described inparagraphs [5009.4852] through [5009.4897] (FIGS. 5347 through 5365);Multiple Tab Web Browsing Function described in paragraphs [5009.4898]through [5009.4926] (FIGS. 5366 through 5388); Multiple Tab Visual DataViewing Function described in paragraphs [5009.4927] through [5009.4955](FIGS. 5389 through 5411); Multiple Tab Document Data Viewing Functiondescribed in paragraphs [5009.4956] through [5009.4984] (FIGS. 5412through 5434); Multiple Tab Email Data Viewing Function described inparagraphs [5009.4985] through [5009.5013] (FIGS. 5435 through 5457);Convenient TV Remote Controlling Function described in paragraphs[5009.5014] through [5009.5034] (FIGS. 5458 through 5471); Form AutoFilling Function described in paragraphs [5009.5035] through [5009.5072](FIGS. 5472 through 5495 e); Hybrid Carrier Function described inparagraphs [5009.5073] through [5009.5105] (FIGS. 5496 through 5522 b);Carrier Current Condition Monitoring Function described in paragraphs[5009.5106] through [5009.5141] (FIGS. 5523 through 5546 c); MemoryDefragmenting Function described in paragraphs [5009.5142] through[5009.5175] (FIGS. 5547 through 5568); Memory Formatting Functiondescribed in paragraphs [5009.5176] through [5009.5209] (FIGS. 5569through 5590); Memory Partitioning Function described in paragraphs[5009.5210] through [5009.5243] (FIGS. 5591 through 5612); TV PhonePausing Function described in paragraphs [5009.5244] through [5009.5268](FIGS. 5613 through 5629); Reflecting Object Displaying Functiondescribed in paragraphs [5009.5269] through [5009.5294] (FIGS. 5630through 5648 c); Alternative TV Program Receiving Function described inparagraphs [5009.5295] through [5009.5325] (FIGS. 5649 through 5670 c);Alternative Radio Program Receiving Function described in paragraphs[5009.5326] through [5009.5356] (FIGS. 5671 through 5692 c); AudiovisualAuto Fading Function described in paragraphs [5009.5357] through[5009.5377] (FIGS. 5693 through 5706); Audio Auto Fading Functiondescribed in paragraphs [5009.5378] through [5009.5398] (FIGS. 5707through 5720); Video-In-Video Displaying Function described inparagraphs [5009.5399] through [5009.5431] (FIGS. 5721 through 5747 b);Pre-Installed Item Purchasing Function described in paragraphs[5009.5432] through [5009.5470] (FIGS. 5748 through 5775 b); MultipleCPU Function described in paragraphs [5009.5471] through [5009.5476](FIGS. 5776 and 5777); Radio Music Downloading Function described inparagraphs [5009.5477] through [5009.5516] (FIGS. 5778 through 5807);File Auto Saving Function described in paragraphs [5009.5517] through[5009.5559] (FIGS. 5808 through 5837 b); TV Tuner Function described inparagraphs [5009.5560] through [5009.5600] (FIGS. 5838 through 5866);GPS Receiver's Log Function described in paragraphs [5009.5601] through[5009.5629] (FIGS. 5867 through 5884 b); Remote Room Light ControllingFunction described in paragraphs [5009.5630] through [5009.5662] (FIGS.5885 through 5906 b); Remote Kitchen Stove Controlling Functiondescribed in paragraphs [5009.5663] through [5009.5695] (FIGS. 5907through 5928 b); Remote Refrigerator Controlling Function described inparagraphs [5009.5696] through [5009.5728] (FIGS. 5929 through 5950 b);Remote Washing Machine Controlling Function described in paragraphs[5009.5729] through [5009.5761] (FIGS. 5951 through 5972 b); RemoteFaucet Controlling Function described in paragraphs [5009.5762] through[5009.5794] (FIGS. 5973 through 5994 b); Remote Door Lock ControllingFunction described in paragraphs [5009.5795] through [5009.5827] (FIGS.5995 through 6016 b); Remote Air Conditioner Controlling Functiondescribed in paragraphs [5009.5828] through [5009.5860] (FIGS. 6017through 6038 b); Remote Vending Machine Controlling Function describedin paragraphs [5009.5861] through [5009.5893] (FIGS. 6039 through 6060b); Remote Video Recorder Controlling Function described in paragraphs[5009.5894] through [5009.5926] (FIGS. 6061 through 6082 b); RemotePrinter Controlling Function described in paragraphs [5009.5927] through[5009.5959] (FIGS. 6083 through 6104 b); Remote Camera ControllingFunction described in paragraphs [5009.5960] through [5009.5992] (FIGS.6105 through 6126 b); Remote TV Tuner Controlling Function described inparagraphs [5009.5993] through [5009.6025] (FIGS. 6127 through 6148 b);Remote Radio Tuner Controlling Function described in paragraphs[5009.6026] through [5009.6058] (FIGS. 6149 through 6170 b); RemoteComputer Controlling Function described in paragraphs [5009.6059]through [5009.6091] (FIGS. 6171 through 6192 b); Remote CarrierControlling Function described in paragraphs [5009.6092] through[5009.6124] (FIGS. 6193 through 6214 b); Remote Food ProcessorControlling Function described in paragraphs [5009.6125] through[5009.6157] (FIGS. 6215 and 6236 b); Remote Dryer Controlling Functiondescribed in paragraphs [5009.6158] through [5009.6190] (FIGS. 6237 and6258 b); Remote Rice Cooker Controlling Function described in paragraphs[5009.6191] through [5009.6223] (FIGS. 6259 and 6280 b); Remote SoundOutputting Device Controlling Function described in paragraphs[5009.6224] through [5009.6256] (FIGS. 6281 and 6302 b); Remote VacuumCleaner Controlling Function described in paragraphs [5009.6257] through[5009.6289] (FIGS. 6303 and 6324 b); Remote FAX Machine ControllingFunction described in paragraphs [5009.6290] through [5009.6322] (FIGS.6325 and 6346 b); Remote Copying Machine Controlling Function describedin paragraphs [5009.6323] through [5009.6355] (FIGS. 6347 and 6368 b);Remote Coffee Maker Controlling Function described in paragraphs[5009.6356] through [5009.6388] (FIGS. 6369 and 6390 b); Remote ScannerControlling Function described in paragraphs [5009.6389] through[5009.6421] (FIGS. 6391 and 6412 b); Remote Clothes Iron ControllingFunction described in paragraphs [5009.6422] through [5009.6454] (FIGS.6413 and 6434 b); Remote Escalator Controlling Function described inparagraphs [5009.6455] through [5009.6487] (FIGS. 6435 and 6456 b);Vending Machine Accessing Function described in paragraphs [5009.6488]through [5009.6527] (FIGS. 6457 through 6485 d); Audiovisual DataShuffling Function described in paragraphs [5009.6528] through[5009.6551] (FIGS. 6486 through 6503 b); Unknown File Icon DisplayingFunction described in paragraphs [5009.6552] through [5009.6575] (FIGS.6504 through 6521 c); Audiovisual Document Producing Function describedin paragraphs [5009.6576] through [5009.6601] (FIGS. 6522 through 6539b); Audiovisual Data Searching Function described in paragraphs[5009.6602] through [5009.6626] (FIGS. 6540 through 6558 b); FingerPrint Log-on Function described in paragraphs [5009.6627] through[5009.6645] (FIGS. 6559 through 6571 c); Voice Print Log-on Functiondescribed in paragraphs [5009.6646] through [5009.6663] (FIGS. 6572through 6583 c); Finger Print Screen Saver Deactivating Functiondescribed in paragraphs [5009.6664] through [5009.6682] (FIGS. 6584through 6596 c); Voice Print Screen Saver Deactivating Functiondescribed in paragraphs [5009.6683] through [5009.6700] (FIGS. 6597through 6608 c); Finger Print Folder Accessing Function described inparagraphs [5009.6701] through [5009.6719] (FIGS. 6609 through 6621 c);Voice Print Folder Accessing Function described in paragraphs[5009.6720] through [5009.6737] (FIGS. 6622 through 6633 c); FingerPrint File Accessing Function described in paragraphs [5009.6738]through [5009.6756] (FIGS. 6634 through 6646 c); Voice Print FileAccessing Function described in paragraphs [5009.6757] through[5009.6774] (FIGS. 6647 through 6658 c); Finger Print Internet AccessingFunction described in paragraphs [5009.6775] through [5009.6793] (FIGS.6659 through 6671 c); Voice Print Internet Accessing Function describedin paragraphs [5009.6794] through [5009.6811] (FIGS. 6672 through 6683c); Finger Print PC Log-on Function described in paragraphs [5009.6812]through [5009.6838] (FIGS. 6684 through 6703 b); Voice Print PC Log-onFunction described in paragraphs [5009.6839] through [5009.6864] (FIGS.6704 through 6722 b); Finger Print PC Screen Saver Deactivating Functiondescribed in paragraphs [5009.6865] through [5009.6891] (FIGS. 6723through 6742 b); Voice Print PC Screen Saver Deactivating Functiondescribed in paragraphs [5009.6892] through [5009.6917] (FIGS. 6743through 6761 b); Finger Print PC Folder Accessing Function described inparagraphs [5009.6918] through [5009.6944] (FIGS. 6762 through 6781 b);Voice Print PC Folder Accessing Function described in paragraphs[5009.6945] through [5009.6970] (FIGS. 6782 through 6800 b); FingerPrint PC File Accessing Function described in paragraphs [5009.6971]through [5009.6997] (FIGS. 6801 through 6820 b); Voice Print PC FileAccessing Function described in paragraphs [5009.6998] through[5009.7023] (FIGS. 6821 through 6839 b); Finger Print PC InternetAccessing Function described in paragraphs [5009.7024] through[5009.7050] (FIGS. 6840 through 6859 b); Voice Print PC InternetAccessing Function described in paragraphs [5009.7051] through[5009.7076] (FIGS. 6860 through 6878 b); Shock Proof Memory Functiondescribed in paragraphs [5009.7077] through [5009.7093] (FIGS. 6879through 6889 b); Remote Audiovisual Device Controlling Functiondescribed in paragraphs [5009.7094] through [5009.7133] (FIGS. 6890through 6916); Direct TV-Audio Phone Switching Function described inparagraphs [5009.7134] through [5009.7157] (FIGS. 6917 through 6932 b);Audiovisual Data Downloading Function described in paragraphs[5009.7158] through [5009.7218] (FIGS. 6933 through 6972); Audio DataDownloading Function described in paragraphs [5009.7219] through[5009.7279] (FIGS. 6973 through 7012); Self-Active Encrypted ImageReader Function described in paragraphs [5009.7280] through [5009.7301](FIGS. 7013 through 7028 c); Robot Remote Controlling Function describedin paragraphs [5009.7302] through [5009.7371] (FIGS. 7029 through 7071b); Home Page Displaying Function described in paragraphs [5009.7372]through [5009.7396] (FIGS. 7072 through 7090); Multiple OS OperatingFunction described in paragraphs [5009.7397] through [5009.7442] (FIGS.7091 through 7130 c); Audiovisual Conversation Data Forwarding Functiondescribed in paragraphs [5009.7443] through [5009.7465] (FIGS. 7131through 7146 b); Audio Conversation Data Forwarding Function describedin paragraphs [5009.7466] through [5009.7488] (FIGS. 7147 through 7162b); Phone Call Auto Forwarding Function described in paragraphs[5009.7489] through [5009.7514] (FIGS. 7163 through 7180 c); WirelessCommunication Method Switching Function described in paragraphs[5009.7515] through [5009.7535] (FIGS. 7181 through 7194 e); DraftedEmail Viewing Function described in paragraphs [5009.7536] through[5009.7585] (FIGS. 7195 through 7236); Email Replying Function describedin paragraphs [5009.7586] through [5009.7617] (FIGS. 7237 through 7262b); Attached File Editing Function described in paragraphs [5009.7618]through [5009.7649] (FIGS. 7263 through 7288 b); Email Audiovisual DataAuto Blocking Function described in paragraphs [5009.7650] through[5009.7673] (FIGS. 7289 through 7306); HDD Stored TV Program ReplayingFunction described in paragraphs [5009.7674] through [5009.7695] (FIGS.7307 through 7322 b); Cooking Menu Auto Implementing Function describedin paragraphs [5009.7696] through [5009.7722] (FIGS. 7323 through 7343b); Micro Wave Oven Auto Alarm Function described in paragraphs[5009.7723] through [5009.7776] (FIGS. 7344 through 7387 b); OvenTemperature Remote Controlling Function described in paragraphs[5009.7777] through [5009.7830] (FIGS. 7388 through 7431 c); AudioAmplifying Function described in paragraphs [5009.7831] through[5009.7848] (FIGS. 7432 through 7443 b); Calorie Calculating Functiondescribed in paragraphs [5009.7849] through [5009.7868] (FIGS. 7444through 7457 b); Sickness Identifying Function described in paragraphs[5009.7869] through [5009.7902] (FIGS. 7458 through 7481 b); WeatherHazard Auto Notifying Function described in paragraphs [5009.7903]through [5009.7955] (FIGS. 7482 through 7517 d); Phone Call AutoForwarding Function described in paragraphs [5009.7956] through[5009.7981] (FIGS. 7518 through 7535 c); Multiple Massaging Functiondescribed in paragraphs [5009.7982] through [5009.8022] (FIGS. 7536through 7566); Microscope Function described in paragraphs [5009.8023]through [5009.8097] (FIGS. 7567 through 7629); Door Auto Lock/UnlockFunction described in paragraphs [5009.8098] through [5009.8139] (FIGS.7630 through 7658 b); Door Auto Close/Open Function described inparagraphs [5009.8140] through [5009.8181] (FIGS. 7659 through 7687 b);Room Light Auto On/Off Function described in paragraphs [5009.8182]through [5009.8223] (FIGS. 7688 through 7716 b); Air Conditioner AutoOn/Off Function described in paragraphs [5009.8224] through [5009.8265](FIGS. 7717 through 7745 b); Heater Auto On/Off Function described inparagraphs [5009.8266] through [5009.8307] (FIGS. 7746 through 7774 b);Faucet Auto On/Off Function described in paragraphs [5009.8308] through[5009.8349] (FIGS. 7775 through 7803 b); Sound Outputting Device AutoOn/Off Function described in paragraphs [5009.8350] through [5009.8391](FIGS. 7804 through 7832 b); Vein Print Log-on Function described inparagraphs [5009.8392] through [5009.8410] (FIGS. 7833 through 7845 c);Vein Print Screen Saver Deactivating Function described in paragraphs[5009.8411] through [5009.8429] (FIGS. 7846 through 7858 c); Vein PrintFolder Accessing Function described in paragraphs [5009.8430] through[5009.8448] (FIGS. 7859 through 7871 c); Vein Print File AccessingFunction described in paragraphs [5009.8449] through [5009.8467] (FIGS.7872 through 7884 c); Vein Print Internet Accessing Function describedin paragraphs [5009.8468] through [5009.8486] (FIGS. 7885 through 7897c); Vein Print PC Log-on Function described in paragraphs [5009.8487]through [5009.8513] (FIGS. 7898 through 7917 b); Vein Print PC ScreenSaver Deactivating Function described in paragraphs [5009.8514] through[5009.8540] (FIGS. 7918 through 7937 b); Vein Print PC Folder AccessingFunction described in paragraphs [5009.8541] through [5009.8567] (FIGS.7938 through 7957 b); Vein Print PC File Accessing Function described inparagraphs [5009.8568] through [5009.8594] (FIGS. 7958 through 7977 b);Vein Print PC Internet Accessing Function described in paragraphs[5009.8595] through [5009.8621] (FIGS. 7978 through 7997 b); RingtoneAuto Updating Function described in paragraphs [5009.8622] through[5009.8643] (FIGS. 7998 through 8013 b); Time Limited Current LocationIdentifying Function described in paragraphs [5009.8644] through[5009.8673] (FIGS. 8014 through 8035 b); In Carrier Message InsertingFunction described in paragraphs [5009.8674] through [5009.8695] (FIGS.8036 through 8050 b); Electric Cable Networking Function described inparagraphs [5009.8696] through [5009.8707] (FIGS. 8051 through 8057);Shoe Sole Pressure Adjusting Function described in paragraphs[5009.8708] through [5009.8741] (FIGS. 8058 through 8080 b); FingerPrint Removal Media Accessing Function described in paragraphs[5009.8742] through [5009.8762] (FIGS. 8081 through 8095 b); Voice PrintRemoval Media Accessing Function described in paragraphs [5009.8763]through [5009.8783] (FIGS. 8096 through 8110 b); Vein Print RemovalMedia Accessing Function described in paragraphs [5009.8784] through[5009.8804] (FIGS. 8111 through 8125 b); Finger Print PC Removal MediaAccessing Function described in paragraphs [5009.8805] through[5009.8833] (FIGS. 8126 through 8145 b); Voice Print PC Removal MediaAccessing Function described in paragraphs [5009.8834] through[5009.8862] (FIGS. 8146 through 8165 b); Vein Print PC Removal MediaAccessing Function described in paragraphs [5009.8863] through[5009.8891] (FIGS. 8166 through 8185 b); Printer Function described inparagraphs [5009.8892] through [5009.8967] (FIGS. 8186 through 8245 f);Scanner Function described in paragraphs [5009.8968] through [5009.9016](FIGS. 8246 through 8284 b); Multiple Signal Transferring Functiondescribed in paragraphs [5009.9017] through [5009.9205] (FIGS. 8285through 8453); Free Access Point Function described in paragraphs[5009.9206] through [5009.9245] (FIGS. 8454 through 8482); Partial BCCEmail Function described in paragraphs [5009.9246] through [5009.9273](FIGS. 8483 through 8504 b); Noise Reversing Function described inparagraphs [5009.9274] through [5009.9291] (FIGS. 8505 through 8516);Door Status Sensoring Function described in paragraphs [5009.9292]through [5009.9345] (FIGS. 8517 through 8557); Drawer Status SensoringFunction described in paragraphs [5009.9346] through [5009.9399] (FIGS.8558 through 8598); Window Status Sensoring Function described inparagraphs [5009.9400] through [5009.9453] (FIGS. 8599 through 8639);Curtain Status Sensoring Function described in paragraphs [5009.9454]through [5009.9509] (FIGS. 8640 through 8680); Gate Status SensoringFunction described in paragraphs [5009.9510] through [5009.9563] (FIGS.8681 through 8721); Stop Watch Function described in paragraphs[5009.9564] through [5009.9584] (FIGS. 8722 through 8736 b);Decrementing Time Function described in paragraphs [5009.9585] through[5009.9607] (FIGS. 8737 through 8753 b); Energy Efficient Multiple CPUFunction described in paragraphs [5009.9608] through [5009.9636] (FIGS.8754 through 8776 b); Content Notifying Function described in paragraphs[5009.9637] through [5009.9681] (FIGS. 8777 through 8809); VirtualTilting Function described in paragraphs [5009.9682] through [5009.9720](FIGS. 8810 through 8840); Virtual Vehicle Tilting Function described inparagraphs [5009.9721] through [5009.9758] (FIGS. 8841 through 8871);Device Approach Notifying Function described in paragraphs [5009.9759]through [5009.9801] (FIGS. 8872 through 8904); Clock Alarm SnoozeFunction described in paragraphs [5009.9802] through [5009.9829] (FIGS.8905 through 8926); News Auto Outputting Function described inparagraphs [5009.9830] through [5009.9867] (FIGS. 8927 through 8958 b);Advertisement Auto Outputting Function described in paragraphs[5009.9868] through [5009.9905] (FIGS. 8959 through 8990 b); Online RPGFunction described in paragraphs [5009.9906] through [5009.10028] (FIGS.8991 through 9098 b); Inter Device Distance Notifying Function describedin paragraphs [5009.10029] through [5009.10065] (FIGS. 9099 through9126); Link Embedded Motion Picture Displaying Function described inparagraphs [5009.10066] through [5009.10089] (FIGS. 9127 through 9141);Audiovisual Meta Data Producing Function described in paragraphs[5009.10090] through [5009.10128] (FIGS. 9142 through 9171 c);Audiovisual Highlight Producing Function described in paragraphs[5009.10129] through [5009.10163] (FIGS. 9172 through 9197); EnhancedAudiovisual Highlight Producing Function described in paragraphs[5009.10164] through [5009.10196] (FIGS. 9198 through 9221); WirelessPower Off Function described in paragraphs [5009.10197] through[5009.10227] (FIGS. 9222 through 9240); Screen Layout Changing Functiondescribed in paragraphs [5009.10228] through [5009.10255] (FIGS. 9241through 9258 b); Face Feature Log-on Function described in paragraphs[5009.10256] through [5009.10273] (FIGS. 9259 through 9270 c); FaceFeature Screen Saver Deactivating Function described in paragraphs[5009.10274] through [5009.10291] (FIGS. 9271 through 9282 c); FaceFeature Folder Accessing Function described in paragraphs [5009.10292]through [5009.10309] (FIGS. 9283 through 9294 c); Face Feature FileAccessing Function described in paragraphs [5009.10310] through[5009.10327] (FIGS. 9295 through 9306 c); Face Feature InternetAccessing Function described in paragraphs [5009.10328] through[5009.10345] (FIGS. 9307 through 9318 c); Face Feature PC Log-onFunction described in paragraphs [5009.10346] through [5009.10371](FIGS. 9319 through 9337 b); Face Feature PC Screen Saver DeactivatingFunction described in paragraphs [5009.10372] through [5009.10397](FIGS. 9338 through 9356 b); Face Feature PC Folder Accessing Functiondescribed in paragraphs [5009.10398] through [5009.10423] (FIGS. 9357through 9375 b); Face Feature PC File Accessing Function described inparagraphs [5009.10424] through [5009.10449] (FIGS. 9376 through 9394b); Face Feature PC Internet Accessing Function described in paragraphs[5009.10450] through [5009.10475] (FIGS. 9395 through 9413 b); FaceFeature Removal Media Accessing Function described in paragraphs[5009.10476] through [5009.10496] (FIGS. 9414 through 9428 b); FaceFeature PC Removal Media Accessing Function described in paragraphs[5009.10497] through [5009.10524] (FIGS. 9429 through 9448 b); SecurityFormatted Removal Media Function described in paragraphs [5009.10525]through [5009.10545] (FIGS. 9449 through 9463 b); Lite SecurityFormatted Removal Media Function described in paragraphs [5009.10546]through [5009.10568] (FIGS. 9464 through 9480 b); Security FormattedFolder Function described in paragraphs [5009.10569] through[5009.10605] (FIGS. 9481 through 9509 b); Host Host Security FormattedFolder Function described in paragraphs [5009.10606] through[5009.10631] (FIGS. 9510 through 9528); Email Security Formatted FolderFunction described in paragraphs [5009.10632] through [5009.10668](FIGS. 9529 through 9557 b); Host Email Security Formatted FolderFunction described in paragraphs [5009.10669] through [5009.10694](FIGS. 9558 through 9576); Secured Email Sending Function described inparagraphs [5009.10695] through [5009.10726] (FIGS. 9577 through 9599c); Secured Email Receiving Function described in paragraphs[5009.10727] through [5009.10746] (FIGS. 9600 through 9613); ReceivedEmail Security Auto Sorting Function described in paragraphs[5009.10747] through [5009.10770] (FIGS. 9614 through 9629 b); SecuredEmail Opening Function described in paragraphs [5009.10771] through[5009.10793] (FIGS. 9630 through 9645 b); Secured Email Attached FileOpening Function described in paragraphs [5009.10794] through[5009.10818] (FIGS. 9646 through 9663 b); Secured Email Attached FileDeleting Function described in paragraphs [5009.10819] through[5009.10845] (FIGS. 9664 through 9679 b); Unsafe Email Host HandledFunction described in paragraphs [5009.10846] through [5009.10873](FIGS. 9680 through 9701 b); Unsafe Attached File Host Handled Functiondescribed in paragraphs [5009.10874] through [5009.10901] (FIGS. 9702through 9723 c); Com Stored Email Viewing Function described inparagraphs [5009.10902] through [5009.10925] (FIGS. 9724 through 9741c); Non-secured Email Forwarding Function described in paragraphs[5009.10926] through [5009.10950] (FIGS. 9742 through 9759 b);Electronic Money Transferring Function described in paragraphs[5009.10951] through [5009.10993] (FIGS. 9760 through 9790 b);Electronic Money Time Identified Transferring Function described inparagraphs [5009.10994] through [5009.11051] (FIGS. 9791 through 9835b); Electronic Money Repeatedly Transferring Function described inparagraphs [5009.11052] through [5009.11117] (FIGS. 9836 through 9888b); Electronic Money Transfer Canceling Function described in paragraphs[5009.11118] through [5009.11194] (FIGS. 9889 through 9952 b);Electronic Money Email Transferring Function described in paragraphs[5009.11195] through [5009.11238] (FIGS. 9953 through 9985 c); MoneyEmail Time Identified Transferring Function described in paragraphs[5009.11239] through [5009.11286] (FIGS. 9986 through 10022 c); MoneyEmail Repeatedly Transferring Function described in paragraphs[5009.11287] through [5009.11338] (FIGS. 10023 through 10063 c);Electronic Money Email Transfer Canceling Function described inparagraphs [5009.11339] through [5009.11405] (FIGS. 10064 through 10119c); Address Book Administrating Function described in paragraphs[5009.11406] through [5009.11451] (FIGS. 10120 through 10152 b); FileSynchronizing Function described in paragraphs [5009.11452] through[5009.11578] (FIGS. 10153 through 10263 b); Folder SynchronizingFunction described in paragraphs [5009.11579] through [5009.11671](FIGS. 10264 through 10342 b); Area Dependent Software ActivatingFunction described in paragraphs [5009.11672] through [5009.11702](FIGS. 10343 through 10366 b); Area Dependent Message DisplayingFunction described in paragraphs [5009.11703] through [5009.11730](FIGS. 10367 through 10388); Visible Light Schedule CommunicatingFunction described in paragraphs [5009.11731] through [5009.11796](FIGS. 10389 through 10437 b); Visible Light Web Address CommunicatingFunction described in paragraphs [5009.11797] through [5009.11862](FIGS. 10438 through 10486 b); Visible Light Software ProgramCommunicating Function described in paragraphs [5009.11863] through[5009.11928] (FIGS. 10487 through 10535 b); Visible Light RestaurantMenu Communicating Function described in paragraphs [5009.11929] through[5009.11994] (FIGS. 10536 through 10584 b); Visible Light TV ListingCommunicating Function described in paragraphs [5009.11995] through[5009.12060] (FIGS. 10585 through 10633 b); Visible Light Movie ListingCommunicating Function described in paragraphs [5009.12061] through[5009.12126] (FIGS. 10634 through 10682 b); Visible Light ProductAdvertisement Communicating Function described in paragraphs[5009.12127] through [5009.12192] (FIGS. 10683 through 10731 b); VisibleLight Message Communicating Function described in paragraphs[5009.12193] through [5009.12258] (FIGS. 10732 through 10780 b); VisibleLight Visual Clip Communicating Function described in paragraphs[5009.12259] through [5009.12324] (FIGS. 10781 through 10829 b); VisibleLight Weather Forecast Communicating Function described in paragraphs[5009.12325] through [5009.12390] (FIGS. 10830 through 10878 b); VisibleLight News Clip Communicating Function described in paragraphs[5009.12391] through [5009.12456] (FIGS. 10879 through 10927 b); VisibleLight Map Clip Communicating Function described in paragraphs[5009.12457] through [5009.12522] (FIGS. 10928 through 10976 b); FileThumbnail Preview Function described in paragraphs [5009.12523] through[5009.12555] (FIGS. 10977 through 11002 b); Taxi Fare Credit CardPayment Function described in paragraphs [5009.12556] through[5009.12632] (FIGS. 11003 through 11067); Taxi Fare Electronic MoneyPayment Function described in paragraphs [5009.12633] through[5009.12712] (FIGS. 11068 through 11132); Taxi Destination IdentifyingFunction described in paragraphs [5009.12713] through [5009.12783](FIGS. 11133 through 11194); Taxi Destination Map Displaying Functiondescribed in paragraphs [5009.12784] through [5009.12860] (FIGS. 11195through 11262); QR Code Schedule Communicating Function described inparagraphs [5009.12861] through [5009.12906] (FIGS. 11263 through 11298b); QR Code Web Address Communicating Function described in paragraphs[5009.12907] through [5009.12952] (FIGS. 11299 through 11334 b); QR CodeSoftware Program Communicating Function described in paragraphs[5009.12953] through [5009.12998] (FIGS. 11335 through 11370 b); QR CodeRestaurant Menu Communicating Function described in paragraphs[5009.12999] through [5009.13044] (FIGS. 11371 through 11406 b); QR CodeTV Listing Communicating Function described in paragraphs [5009.13045]through [5009.13090] (FIGS. 11407 through 11442 b); QR Code MovieListing Communicating Function described in paragraphs [5009.13091]through [5009.13136] (FIGS. 11443 through 11478 b); QR Code ProductAdvertisement Communicating Function described in paragraphs[5009.13137] through [5009.13182] (FIGS. 11479 through 11514 b); QR CodeMessage Communicating Function described in paragraphs [5009.13183]through [5009.13228] (FIGS. 11515 through 11550 b); QR Code Visual ClipCommunicating Function described in paragraphs [5009.13229] through[5009.13274] (FIGS. 11551 through 11586 b); QR Code Weather ForecastCommunicating Function described in paragraphs [5009.13275] through[5009.13320] (FIGS. 11587 through 11622 b); QR Code News ClipCommunicating Function described in paragraphs [5009.13321] through[5009.13366] (FIGS. 11623 through 11658 b); QR Code Map ClipCommunicating Function described in paragraphs [5009.13367] through[5009.13412] (FIGS. 11659 through 11694 b); QR Code Software ActivatingFunction described in paragraphs [5009.13413] through [5009.13458](FIGS. 11695 through 11730 b); RFID Schedule Communicating Functiondescribed in paragraphs [5009.13459] through [5009.13508] (FIGS. 11731through 11770 b); RFID Web Address Communicating Function described inparagraphs [5009.13509] through [5009.13558] (FIGS. 11771 through 11810b); RFID Software Program Communicating Function described in paragraphs[5009.13559] through [5009.13608] (FIGS. 11811 through 11850 b); RFIDRestaurant Menu Communicating Function described in paragraphs[5009.13609] through [5009.13658] (FIGS. 11851 through 11890 b); RFID TVListing Communicating Function described in paragraphs [5009.13659]through [5009.13708] (FIGS. 11891 through 11930 b); RFID Movie ListingCommunicating Function described in paragraphs [5009.13709] through[5009.13758] (FIGS. 11931 through 11970 b); RFID Product AdvertisementCommunicating Function described in paragraphs [5009.13759] through[5009.13808] (FIGS. 11971 through 12010 b); RFID Message CommunicatingFunction described in paragraphs [5009.13809] through [5009.13858](FIGS. 12011 through 12050 b); RFID Visual Clip Communicating Functiondescribed in paragraphs [5009.13859] through [5009.13908] (FIGS. 12051through 12090 b); RFID Weather Forecast Communicating Function describedin paragraphs [5009.13909] through [5009.13958] (FIGS. 12091 through12130 b); RFID News Clip Communicating Function described in paragraphs[5009.13959] through [5009.14008] (FIGS. 12131 through 12170 b); RFIDMap Clip Communicating Function described in paragraphs [5009.14009]through [5009.14058] (FIGS. 12171 through 12210 b); RFID SoftwareActivating Function described in paragraphs [5009.14059] through[5009.14108] (FIGS. 12211 through 12250 b); RFID Software AutoActivating Function described in paragraphs [5009.14109] through[5009.14158] (FIGS. 12251 through 12290 b); Carrier Arrival TimeDisplaying Function described in paragraphs [5009.14159] through[5009.14283] (FIGS. 12291 through 12401); Multiple Audio OutputtingFunction described in paragraphs [5009.14284] through [5009.14310](FIGS. 12402 through 12419); Closest Device Notifying Function describedin paragraphs [5009.14311] through [5009.14416] (FIGS. 12420 through12515); Print Screen Function described in paragraphs [5009.14417]through [5009.14474] (FIGS. 12516 through 12559 b); Caller AnsweringMachine Activating Function described in paragraphs [5009.14475] through[5009.14513] (FIGS. 12560 through 12587); Audiovisual Answering MachineFunction described in paragraphs [5009.14514] through [5009.14546](FIGS. 12588 through 12611); Answering Machine Message ForwardingFunction described in paragraphs [5009.14547] through [5009.14607](FIGS. 12612 through 12657); Area Map Displaying Function described inparagraphs [5009.14608] through [5009.14679] (FIGS. 12658 through 12721b); Road Map Displaying Function described in paragraphs [5009.14680]through [5009.14752] (FIGS. 12722 through 12785 b); Email ReadingFunction described in paragraphs [5009.14753] through [5009.14781](FIGS. 12786 through 12805 c); Stand Alone Email Function described inparagraphs [5009.14782] through [5009.14850] (FIGS. 12806 through 12857b); TV Seamless Viewing Function described in paragraphs [5009.14851]through [5009.14896] (FIGS. 12858 through 12895); Multiple Movable TabWeb Browsing Function described in paragraphs [5009.14897] through[5009.14975] (FIGS. 12896 through 12966); Multiple Movable Tab VisualData Viewing Function described in paragraphs [5009.14976] through[5009.15054] (FIGS. 12967 through 13037); Multiple Movable Tab DocumentData Viewing Function described in paragraphs [5009.15055] through[5009.15133] (FIGS. 13038 through 13108); Multiple Movable Tab EmailData Viewing Function described in paragraphs [5009.15134] through[5009.15212] (FIGS. 13109 through 13179); Lost Com Device MemoryErasing/Rescuing Function described in paragraphs [5009.15213] through[5009.15275] (FIGS. 13180 through 13231 c); Lost Com Device BeaconingFunction described in paragraphs [5009.15276] through [5009.15353](FIGS. 13232 through 13296); Area & Country Name Displaying Functiondescribed in paragraphs [5009.15354] through [5009.15437] (FIGS. 13297through 13371); 3D Desktop Function described in paragraphs [5009.15438]through [5009.15536] (FIGS. 13372 through 13457); Carrier AutoAnnouncing Function described in paragraphs [5009.15537] through[5009.15586] (FIGS. 13458 through 13497 b); Virtual Folder DisplayingFunction described in paragraphs [5009.15587] through [5009.15647](FIGS. 13498 through 13548 b); In-carrier Location Notifying Functiondescribed in paragraphs [5009.15648] through [5009.15703] (FIGS. 13549through 13595 c); Address Map Auto Displaying Function described inparagraphs [5009.15704] through [5009.15771] (FIGS. 13596 through 13650c); Brain Wave Device Controlling Function described in paragraphs[5009.15772] through [5009.15806] (FIGS. 13651 through 13679 b); BrainWave Sentence Composing Function described in paragraphs [5009.15807]through [5009.15829] (FIGS. 13680 through 13696); Wheel StandingFunction described in paragraphs [5009.15830] through [5009.15858](FIGS. 13697 through 13719); Robot Body Balancing Function described inparagraphs [5009.15859] through [5009.15905] (FIGS. 13720 through13760); Robot Leg Balancing Function described in paragraphs[5009.15906] through [5009.15952] (FIGS. 13761 through 13801); RobotHead Balancing Function described in paragraphs [5009.15953] through[5009.15999] (FIGS. 13802 through 13842); Robot Upper Body BalancingFunction described in paragraphs [5009.16000] through [5009.16045](FIGS. 13843 through 13883); Digital Television Function described inparagraphs [5009.16046] through [5009.16075] (FIGS. 13884 through13906); Total Price Calculating Function described in paragraphs[5009.16076] through [5009.16166] (FIGS. 13907 through 13985 c); BrainWave Carrier Controlling Function described in paragraphs [5009.16167]through [5009.16202] (FIGS. 13986 through 14015 b); Electronic BillboardControlling Function described in paragraphs [5009.16203] through[5009.16323] (FIGS. 14016 through 14123 e); Common Phone Number Functiondescribed in paragraphs [5009.16324] through [5009.16424] (FIGS. 14124through 14212 c); Hybrid Common Phone Number Function described inparagraphs [5009.16425] through [5009.16525] (FIGS. 14213 through 14301c); Ringtone Volume Auto Adjusting Function described in paragraphs[5009.16526] through [5009.16547] (FIGS. 14302 through 14317 b);Ringtone Type Auto Selecting Function described in paragraphs[5009.16548] through [5009.16575] (FIGS. 14318 through 14339 b);Television Chatting Function described in paragraphs [5009.16576]through [5009.16650] (FIGS. 14340 through 14405); Device BatteryCharging Function described in paragraphs [5009.16651] through[5009.16726] (FIGS. 14406 through 14471 b); Hybrid Battery SolarOperating Function described in paragraphs [5009.16727] through[5009.16829] (FIGS. 14472 through 14561); Backup Solar Battery OperatingFunction described in paragraphs [5009.16830] through [5009.16932](FIGS. 14562 through 14651); Hybrid Access Point Function described inparagraphs [5009.16933] through [5009.17169] (FIGS. 14652 through 14878g); Earphone Location Identifying Function described in paragraphs[5009.17170] through [5009.17266] (FIGS. 14879 through 14961);Microphone Location Identifying Function described in paragraphs[5009.17267] through [5009.17355] (FIGS. 14962 through 15036); EventTriggered Auto Audiovisual Recording Function described in paragraphs[5009.17356] through [5009.17402] (FIGS. 15037 through 15072 b); EventTriggered Auto Audio Recording Function described in paragraphs[5009.17403] through [5009.17449] (FIGS. 15073 through 15108 b);Audiovisual Message Bulk Transferring Function described in paragraphs[5009.17450] through [5009.17501] (FIGS. 15109 through 15150 b);Multiple Party Conversing Function described in paragraphs [5009.17502]through [5009.17670] (FIGS. 15151 through 15299); Window MonitoringFunction described in paragraphs [5009.17671] through [5009.17700](FIGS. 15300 through 15321 b); Window Status Monitoring Functiondescribed in paragraphs [5009.17701] through [5009.17730] (FIGS. 15322through 15343 b); Door Monitoring Function described in paragraphs[5009.17731] through [5009.17760] (FIGS. 15344 through 15365 b); DoorMonitoring Function described in paragraphs [5009.17761] through[5009.17790] (FIGS. 15366 through 15387 b); Push-To-Talk Functiondescribed in paragraphs [5009.17791] through [5009.18008] (FIGS. 15388through 15586 cPush-To-T); Door Open Monitoring Function described inparagraphs [5009.18009] through [5009.18065] (FIGS. 15587 through 15633b); Window Open Monitoring Function described in paragraphs [5009.18066]through [5009.18122] (FIGS. 15634 through 15680 b); Lock Open MonitoringFunction described in paragraphs [5009.18123] through [5009.18179](FIGS. 15681 through 15727 b); Destination Proceeding Function describedin paragraphs [5009.18180] through [5009.18265] (FIGS. 15728 through15803 d); Driver's Eye Monitoring Safety Function described inparagraphs [5009.18266] through [5009.18316] (FIGS. 15804 through15845); Driver's Head Monitoring Safety Function described in paragraphs[5009.18317] through [5009.18365] (FIGS. 15846 through 15885); DrawerOpen Monitoring Function described in paragraphs [5009.18366] through[5009.18422] (FIGS. 15886 through 15932 b); Curtain Open MonitoringFunction described in paragraphs [5009.18423] through [5009.18479](FIGS. 15933 through 15979 b); Gate Open Monitoring Function describedin paragraphs [5009.18480] through [5009.18536] (FIGS. 15980 through16026 b); Faucet Open Monitoring Function described in paragraphs[5009.18537] through [5009.18593] (FIGS. 16027 through 16073 b); HybridRefrigerator Function described in paragraphs [5009.18594] through[5009.18695] (FIGS. 16074 through 16159 b); Multiple Purpose ChamberFunction described in paragraphs [5009.18696] through [5009.18869](FIGS. 16160 through 16312 c); Audiovisual Quality Auto AdjustingFunction described in paragraphs [5009.18870] through [5009.18930](FIGS. 16313 through 16363 b); Audio Quality Auto Adjusting Functiondescribed in paragraphs [5009.18931] through [5009.18991] (FIGS. 16364through 16414 b); TV Phone Quality Auto Adjusting Function described inparagraphs [5009.18992] through [5009.19100] (FIGS. 16415 through16512); Voice Phone Quality Auto Adjusting Function described inparagraphs [5009.19101] through [5009.19209] (FIGS. 16513 through16610); Television Related Audiovisual Downloading Function described inparagraphs [5009.19210] through [5009.19299] (FIGS. 16611 through16687); Radio Related Audio Downloading Function described in paragraphs[5009.19300] through [5009.19389] (FIGS. 16688 through 16764); HeaderDisplaying Function described in paragraphs [5009.19390] through[5009.19464] (FIG. 16765 through FIG. 16826 b); Footer DisplayingFunction described in paragraphs [5009.19465] through [5009.19539] (FIG.16827 through FIG. 16888 b); Location Scheduled Notifying Functiondescribed in paragraphs [5009.19540] through [5009.19602] (FIG. 16889through FIG. 16941 e); Zone Leaving Notifying Function described inparagraphs [5009.19603] through [5009.19675] (FIG. 16942 through FIG.17005 d); Zone Entering Notifying Function described in paragraphs[5009.19676] through [5009.19748] (FIG. 17006 through FIG. 17069 d);Power Off Notifying Function described in paragraphs [5009.19749]through [5009.19794] (FIG. 17070 through FIG. 17106 d); Power OnNotifying Function described in paragraphs [5009.19795] through[5009.19840] (FIG. 17107 through FIG. 17143 d); Security Alarm OnNotifying Function described in paragraphs [5009.19841] through[5009.19886] (FIG. 17144 through FIG. 17180 d); Security Alarm OffNotifying Function described in paragraphs [5009.19887] through[5009.19932] (FIG. 17181 through FIG. 17217 d); Email Transfer NotifyingFunction described in paragraphs [5009.19933] through [5009.19978] (FIG.17218 through FIG. 17254 d); Email Reception Notifying Functiondescribed in paragraphs [5009.19979] through [5009.20024] (FIG. 17255through FIG. 17291 d); Making Phone Call Notifying Function described inparagraphs [5009.20025] through [5009.20070] (FIG. 17292 through FIG.17328 d); Phone Call Reception Notifying Function described inparagraphs [5009.20071] through [5009.20116] (FIG. 17329 through FIG.17365 d); Key Pressed Notifying Function described in paragraphs[5009.20117] through [5009.20162] (FIG. 17366 through FIG. 17402 d);Software Activation Notifying Function described in paragraphs[5009.20163] through [5009.20208] (FIG. 17403 through FIG. 17439 d);Document Opening Notifying Function described in paragraphs [5009.20209]through [5009.20254] (FIG. 17440 through FIG. 17476 d); Specified EventNotifying Function described in paragraphs [5009.20255] through[5009.20315] (FIG. 17477 through FIG. 17527 d); Television Phone AutoBackup Function described in paragraphs [5009.20316] through[5009.20447] (FIG. 17528 through FIG. 17645 b); File Auto SavingFunction described in paragraphs [5009.20448] through [5009.20495] (FIG.17646 through FIG. 17678 b); File Compressing Function described inparagraphs [5009.20496] through [5009.20559] (FIG. 17679 through FIG.17727 e); Multiple Phone Number Billing Function described in paragraphs[5009.20560] through [5009.20609] (FIG. 17728 through FIG. 17771);Multiple Device Door Unlocking Function described in paragraphs[5009.20610] through [5009.20685] (FIG. 17772 through FIG. 17832 c);Multiple Device Door Locking Function described in paragraphs[5009.20686] through [5009.20761] (FIG. 17833 through FIG. 17893 c);Phone Call Making Log Recording Function described in paragraphs[5009.20762] through [5009.20815] (FIG. 17894 through FIG. 17938 d);Phone Call Receiving Log Recording Function described in paragraphs[5009.20816] through [5009.20867] (FIG. 17939 through FIG. 17981 d);Phone Call Making Log Exporting Function described in paragraphs[5009.20868] through [5009.20917] (FIG. 17982 through FIG. 18022 d);Phone Call Receiving Log Exporting Function described in paragraphs[5009.20918] through [5009.20967] (FIG. 18023 through FIG. 18063 d);Phone Call Making Log Synchronizing Function described in paragraphs[5009.20968] through [5009.21021] (FIG. 18064 through FIG. 181060; PhoneCall Receiving Log Synchronizing Function described in paragraphs[5009.21022] through [5009.21075] (FIG. 18107 through FIG. 181490; 3DAdvertisement Displaying Function described in paragraphs [5009.21076]through [5009.21217] (FIG. 18150 through FIG. 18277); AudiovisualLocation Capability Function described in paragraphs [5009.21218]through [5009.21276] (FIG. 18278 through FIG. 18325 c); Location AudioNotifying Function described in paragraphs [5009.21277] through[5009.21319] (FIG. 18326 through FIG. 18359 b); Answering MachineLocation Recording Function described in paragraphs [5009.21320] through[5009.21388] (FIG. 18360 through FIG. 18417 e); Visual Phone FileSharing Function described in paragraphs [5009.21389] through[5009.21526] (FIG. 18418 through FIG. 18540 b); Visual Phone MagnifyingFunction described in paragraphs [5009.21527] through [5009.21629] (FIG.18541 through FIG. 18631); Multiple Home Page Displaying Functiondescribed in paragraphs [5009.21630] through [5009.21700] (FIG. 18632through FIG. 18693 b FIG. 18632 through FIG. 18693 b); Multiple VisualPhone Party Location Identifying Function described in paragraphs[5009.21701] through [5009.21796] (FIG. 18694 through FIG. 18778 g);Individual Party Conversation Replaying Function described in paragraphs[5009.21797] through [5009.21962] (FIG. 18779 through FIG. 18929 d);Multiple Phone Notifying Function described in paragraphs [5009.21963]through [5009.22050] (FIG. 18930 through FIG. 19004 i); Multiple PhoneDial Tone Function described in paragraphs [5009.22051] through[5009.22160] (FIG. 19005 through FIG. 19101 f); Multiple Phone New PartyJoining Function described in paragraphs [5009.22161] through[5009.22276] (FIG. 19102 through FIG. 19206 j); and Music PropertySetting Function described in paragraphs [5009.22277] through[5009.22302] (FIG. 19207 through FIG. 19226 b).

The invention claimed is:
 1. A communication device comprising: amicrophone; a speaker; an input device; a display; an antenna; apower-off notification implementer, wherein upon the power of anotherdevice is identified to be turned off, a power-off notification isretrieved and provided to the user of said communication device; apower-off location notifying implementer, wherein a power-off locationwhich is the location of said another device at which the power of saidanother device is turned off is retrieved and provided to the user ofsaid communication device; a header displaying implementer, wherein whena first document is transferred from said another device to saidcommunication device, a header relevant data is transferred from saidanother device to said communication device together with said firstdocument, wherein said header relevant data indicates the text, fonttype, font size, font color, and/or location of a header of said firstdocument, wherein when said first document is retrieved and displayed onsaid communication device, said header is retrieved and displayed inaccordance with said text, said font type, said font size, said fontcolor, and/or said location of said header, which are identified by saidanother device in advance to transferring said header relevant data fromsaid another device to said communication device; a footer displayingimplementer, wherein when a second document is transferred from saidanother device to said communication device, a footer relevant data istransferred from said another device to said communication devicetogether with said second document, wherein said footer relevant dataindicates the text, font type, font size, font color, and/or location ofa footer of said second document, wherein when said second document isretrieved and displayed on said communication device, said footer isretrieved and displayed in accordance with said text, said font type,said font size, said font color, and/or said location of said footer,which are identified by said another device in advance to transferringsaid footer relevant data from said another device to said communicationdevice; a zone leaving notifying implementer, wherein when said anotherdevice is identified to be leaving from a specific geographic zoneidentified by said communication device, a zone leaving notice isretrieved and provided to the user of said communication device; and azone entering notifying implementer, wherein when said another device isidentified to be entering into said specific geographic zone identifiedby said communication device, a zone entering notice is retrieved andprovided to the user of said communication device.
 2. The communicationdevice of claim 1, wherein said communication device is a handhelddevice.
 3. The communication device of claim 1, wherein saidcommunication device is operable to implement voice communication. 4.The communication device of claim 1, wherein said communication deviceis operable to implement voice communication via said antenna.
 5. Thecommunication device of claim 1, wherein said communication device isconnected with said another device via a network.
 6. The communicationdevice of claim 1, wherein said power-off notification is provided tothe user of said communication device by displaying a specific messageon said communication device.
 7. A system comprising: a communicationdevice comprising a microphone, a speaker, an input device, a display,and an antenna; a power-off notification implementer, wherein upon thepower of another device is identified to be turned off, a power-offnotification is retrieved and provided to the user of said communicationdevice; a power-off location notifying implementer, wherein a power-offlocation which is the location of said another device at which the powerof said another device is turned off is retrieved and provided to theuser of said communication device; a header displaying implementer,wherein when a first document is transferred from said another device tosaid communication device, a header relevant data is transferred fromsaid another device to said communication device together with saidfirst document, wherein said header relevant data indicates the text,font type, font size, font color, and/or location of a header of saidfirst document, wherein when said first document is retrieved anddisplayed on said communication device, said header is retrieved anddisplayed in accordance with said text, said font type, said font size,said font color, and/or said location of said header, which areidentified by said another device in advance to transferring said headerrelevant data from said another device to said communication device; afooter displaying implementer, wherein when a second document istransferred from said another device to said communication device, afooter relevant data is transferred from said another device to saidcommunication device together with said second document, wherein saidfooter relevant data indicates the text, font type, font size, fontcolor, and/or location of a footer of said second document, wherein whensaid second document is retrieved and displayed on said communicationdevice, said footer is retrieved and displayed in accordance with saidtext, said font type, said font size, said font color, and/or saidlocation of said footer, which are identified by said another device inadvance to transferring said footer relevant data from said anotherdevice to said communication device; a zone leaving notifyingimplementer, wherein when said another device is identified to beleaving from a specific geographic zone identified by said communicationdevice, a zone leaving notice is retrieved and provided to the user ofsaid communication device; and a zone entering notifying implementer,wherein when said another device is identified to be entering into saidspecific geographic zone identified by said communication device, a zoneentering notice is retrieved and provided to the user of saidcommunication device.
 8. The system of claim 7, wherein saidcommunication device is a handheld device.
 9. The system of claim 7,wherein said communication device is operable to implement voicecommunication.
 10. The system of claim 7, wherein said communicationdevice is operable to implement voice communication via said antenna.11. The system of claim 7, wherein said communication device isconnected with said another device via a network.
 12. The system ofclaim 7, wherein said power-off notification is provided to the user ofsaid communication device by displaying a specific message on saidcommunication device.
 13. A method for a communication device comprisinga microphone, a speaker, an input device, a display, and an antenna,said method comprising: a power-off notification implementing step,wherein upon the power of another device is identified to be turned off,a power-off notification is retrieved and provided to the user of saidcommunication device; a power-off location notifying implementing step,wherein a power-off location which is the location of said anotherdevice at which the power of said another device is turned off isretrieved and provided to the user of said communication device; aheader displaying implementing step, wherein when a first document istransferred from said another device to said communication device, aheader relevant data is transferred from said another device to saidcommunication device together with said first document, wherein saidheader relevant data indicates the text, font type, font size, fontcolor, and/or location of a header of said first document, wherein whensaid first document is retrieved and displayed on said communicationdevice, said header is retrieved and displayed in accordance with saidtext, said font type, said font size, said font color, and/or saidlocation of said header, which are identified by said another device inadvance to transferring said header relevant data from said anotherdevice to said communication device; a footer displaying implementingstep, wherein when a second document is transferred from said anotherdevice to said communication device, a footer relevant data istransferred from said another device to said communication devicetogether with said second document, wherein said footer relevant dataindicates the text, font type, font size, font color, and/or location ofa footer of said second document, wherein when said second document isretrieved and displayed on said communication device, said footer isretrieved and displayed in accordance with said text, said font type,said font size, said font color, and/or said location of said footer,which are identified by said another device in advance to transferringsaid footer relevant data from said another device to said communicationdevice; a zone leaving notifying implementing step, wherein when saidanother device is identified to be leaving from a specific geographiczone identified by said communication device, a zone leaving notice isretrieved and provided to the user of said communication device; and azone entering notifying implementing step, wherein when said anotherdevice is identified to be entering into said specific geographic zoneidentified by said communication device, a zone entering notice isretrieved and provided to the user of said communication device.
 14. Themethod of claim 13, wherein said communication device is a handhelddevice.
 15. The method of claim 13, wherein said communication device isoperable to implement voice communication.
 16. The method of claim 13,wherein said communication device is operable to implement voicecommunication via said antenna.
 17. The method of claim 13, wherein saidcommunication device is connected with said another device via anetwork.
 18. The method of claim 13, wherein said power-off notificationis provided to the user of said communication device by displaying aspecific message on said communication device.